SDA's simulation reports are (wrongly) contacting our SOCKS server
lbarman opened this issue · comments
Ludovic Barman commented
1 : ( monitor.send: 209) - Couldn't send to monitor-sink: write tcp 127.0.0.1:44422->127.0.0.1:10000: write: broken pipe
E : ( prifi-socks.StartSocksServer: 212) - SOCKS PriFi Server : got a new connection, assigned id 2389650421
E : ( prifi-socks.StartSocksServer: 212) - SOCKS PriFi Server : got a new connection, assigned id 3641582335
E : ( prifi-socks.StartSocksServer: 212) - SOCKS PriFi Server : got a new connection, assigned id 3815083031
1 : ( monitor.send: 209) - Couldn't send to monitor-sink: write tcp 127.0.0.1:44422->127.0.0.1:10000: write: broken pipe
1 : ( monitor.send: 209) - Couldn't send to monitor-sink: write tcp 127.0.0.1:44422->127.0.0.1:10000: write: broken pipe
1 : ( monitor.send: 209) - Couldn't send to monitor-sink: write tcp 127.0.0.1:44422->127.0.0.1:10000: write: broken pipe
1 : ( monitor.send: 209) - Couldn't send to monitor-sink: write tcp 127.0.0.1:44422->127.0.0.1:10000: write: broken pipe
E : ( monitor.(*singleMeasure).Record: 98) - Error sending SingleMeasure bandwidth_root_rx to monitor: Could not send any measures
(no socks connection should every happen in simulation at this point)
Ludovic Barman commented
This behavior has not been experienced lately.