Snowflake proxy seems to dry out

I’ve cloned snowflake from gitlab a couple of days ago, installed GO1.19 and initiated build process ending up in a proxy binary.
No, if starting this proxy (with logging) it reports some activity. That seem to be fine.

Some findings:

  1. Many log files get written twice! Is that intended? Some samples:
2022/10/10 15:54:28 Connection successful.
2022/10/10 15:54:28 Connection successful.
2022/10/10 15:54:28 OnOpen channel
2022/10/10 15:54:28 OnOpen channel
2022/10/10 15:54:28 connected to relay: wss://snowflake.torproject.net/
2022/10/10 15:54:28 connected to relay: wss://snowflake.torproject.net/
  1. Process establishes 8 LWPs (Threads).
  2. After approx. five to six hours activity seem to dry out. I’ve seen this now at least three times. The only activity is repeating these lines:
2022/10/09 12:54:54 In the last 1h0m0s, there were 8 connections. Traffic Relayed ↑ 27 MB, ↓ 5 MB.
2022/10/09 13:54:54 In the last 1h0m0s, there were 0 connections. Traffic Relayed ↑ 0 B, ↓ 0 B.
2022/10/09 14:54:54 In the last 1h0m0s, there were 0 connections. Traffic Relayed ↑ 0 B, ↓ 0 B.
2022/10/09 15:54:54 In the last 1h0m0s, there were 0 connections. Traffic Relayed ↑ 0 B, ↓ 0 B.
2022/10/09 16:54:54 In the last 1h0m0s, there were 0 connections. Traffic Relayed ↑ 0 B, ↓ 0 B.
2022/10/09 17:54:54 In the last 1h0m0s, there were 0 connections. Traffic Relayed ↑ 0 B, ↓ 0 B.
2022/10/09 18:54:54 In the last 1h0m0s, there were 0 connections. Traffic Relayed ↑ 0 B, ↓ 0 B.

Is that normal? My plan was to have it run on a small box (similar to Rasperry Pi) 24/7.

Hi.

You could run:

proxy -verbose

to get more output from the log. That works for a standalone. I think docker has a verbose option too.

There have been a few stretches of 0 traffic relayed in the last 24 hours. I’ve had the same on two machines.

Double entries are not a problem. It’s the way the output works.

Β·Β·Β·

On Oct 10, 2022, at 9:39 AM, mjacobs-de via Tor Project Forum notifications@torproject1.discoursemail.com wrote:

| mjacobs-de
October 10 |

  • | - |

I’ve cloned snowflake from gitlab a couple of days ago, installed GO1.19 and initiated build process ending up in a proxy binary.
No, if starting this proxy (with logging) it reports some activity. That seem to be fine.

Some findings:

  1. Many log files get written twice! Is that intended? Some samples:
2022/10/10 15:54:28 Connection successful.
2022/10/10 15:54:28 Connection successful.
2022/10/10 15:54:28 OnOpen channel
2022/10/10 15:54:28 OnOpen channel
2022/10/10 15:54:28 connected to relay: wss://snowflake.torproject.net/
2022/10/10 15:54:28 connected to relay: wss://snowflake.torproject.net/

  1. Process establishes 8 LWPs (Threads).
  2. After approx. five to six hours activity seem to dry out. I’ve seen this now at least three times. The only activity is repeating these lines:
2022/10/09 12:54:54 In the last 1h0m0s, there were 8 connections. Traffic Relayed ↑ 27 MB, ↓ 5 MB.
2022/10/09 13:54:54 In the last 1h0m0s, there were 0 connections. Traffic Relayed ↑ 0 B, ↓ 0 B.
2022/10/09 14:54:54 In the last 1h0m0s, there were 0 connections. Traffic Relayed ↑ 0 B, ↓ 0 B.
2022/10/09 15:54:54 In the last 1h0m0s, there were 0 connections. Traffic Relayed ↑ 0 B, ↓ 0 B.
2022/10/09 16:54:54 In the last 1h0m0s, there were 0 connections. Traffic Relayed ↑ 0 B, ↓ 0 B.
2022/10/09 17:54:54 In the last 1h0m0s, there were 0 connections. Traffic Relayed ↑ 0 B, ↓ 0 B.
2022/10/09 18:54:54 In the last 1h0m0s, there were 0 connections. Traffic Relayed ↑ 0 B, ↓ 0 B.

Is that normal? My plan was to have it run on a small box (similar to Rasperry Pi) 24/7.


Visit Topic or reply to this email to respond.

To unsubscribe from these emails, click here.

1 Like

Thank you.
Today draining does not seem to happen, so I’ll move this version to the little box in the next days.

This topic was automatically closed 5 hours after the last reply. New replies are no longer allowed.