Tempo cannot receive span with wal open error on Windows

I create a simple tempo to receive trace like below:

server:
  http_listen_port: 3200
  grpc_listen_port: 9096

distributor:
  receivers:
    zipkin:
  log_received_spans:
    enabled: true

storage:
  trace:
    backend: local
    wal:
      path: ../data/wal
    local:
      path: ../data/blocks

Try to send trace by postman to localhost:9411 with body:

[{ 
 "id": "1234", 
 "traceId": "0123456789abcdef", 
 "timestamp": 1608239395286533, 
 "duration": 100000, 
 "name": "span from Postman", 
 "tags": { 
    "http.method": "GET", 
    "http.path": "/api" 
  }, 
  "localEndpoint": { 
    "serviceName": "shell script" 
  } 
}]

Then in tempo it complain with an error:

level=info ts=2022-09-12T08:22:59.6774562Z caller=distributor.go:550 msg=received spanid=0000000000001234 traceid=00000000000000000123456789abcdef

level=warn ts=2022-09-12T08:22:59.6786623Z caller=grpc_logging.go:43 method=/tempopb.Pusher/PushBytesV2 duration=0s err=“open …\data\wal\ee02a5d5-246f-4bec-a657-3e1f34a34abc:single-tenant:v2:snappy:v2: The filename, directory name, or volume label syntax is incorrect.” msg=gRPC

level=error ts=2022-09-12T08:22:59.6786623Z caller=rate_limited_logger.go:27 msg=“pusher failed to consume trace data” err="rpc error: code = Unknown desc = open …\data\wal\ee02a5d5-246f-4bec-a657-3e1f34a34abc:single-tenant:v2:snappy:v2: The filename, directory name, or volume label syntax is incorrect.

Anyone have an idea on this issue? thanks.

Hi @bmkhoaw! This PR addresses the issue you’re seeing. The problem is that Windows doesn’t work with filenames that contain colons :. That’s why you see that error The filename, directory name, or volume label syntax is incorrect.

1 Like

Hi @mariorodriguez!
Thanks for the information. May I know when it is released or can I have an early build to test, or is there any workaround?

I am also wondering if this issue persisted for Windows then how can Tempo works on Windows so far?

There is not workaround I’m aware of :frowning: What we (the tempo team) should do is push to merge a solution, that PR or a different one.

As said in the issue, we’re surprise of Tempo not working on Windows. It must have been broken for a long time or never worked. Apologies.

This is really sad. Hopefully it is merged and released soon due to its blocking nature.