Gitaly does not start

Hi, I hope I'm posting this in the right place...

after updating my gitlab on arch (via repo) from 9 to 10, Gitaly refuses to start. I have not edited the config.toml at all and it is at its repo default.

This is the error I get: INFO[0000] Starting Gitaly version="Gitaly, version 0.43.0, built 20171006.023852" WARN[0000] git path not configured. Using default path resolution resolvedPath=/usr/bin/git FATA[0000] load config config_path=/etc/gitlab-gitaly/config.toml error="exit status 127; stderr: \"\""

This is the repo default config.toml:

# Example Gitaly configuration file

socket_path = "/var/lib/gitlab/sockets/gitlab-gitaly.socket"

# # Optional: listen on a TCP socket. This is insecure (no authentication)
# listen_addr = "localhost:9999"
#

# # Optional: export metrics via Prometheus
# prometheus_listen_addr = "localhost:9236"
#

# # Git executable settings
# [git]
# bin_path = "/usr/bin/git"

[[storage]]
name = "default"
path = "/var/lib/gitlab/repositories"

# # You can optionally configure more storages for this Gitaly instance to serve up
#
# [[storage]]
# name = "other_storage"
# path = "/mnt/other_storage/repositories"
#

# # You can optionally configure Gitaly to output JSON-formatted log messages to stdout
# [logging]
# format = "json"
# # Additionally exceptions can be reported to Sentry
# sentry_dsn = "https://<key>:<secret>@sentry.io/<project>"

# # You can optionally configure Gitaly to record histogram latencies on GRPC method calls
# [prometheus]
# grpc_latency_buckets = [0.001, 0.005, 0.025, 0.1, 0.5, 1.0, 10.0, 30.0, 60.0, 300.0, 1500.0]

[gitaly-ruby]
# The directory where gitaly-ruby is installed
dir = "/usr/share/webapps/gitlab-gitaly/ruby"

[gitlab-shell]
# The directory where gitlab-shell is installed
dir = "/usr/share/webapps/gitlab-shell"

# # You can adjust the concurrency of each RPC endpoint
# [[concurrency]]
# rpc = "/gitaly.RepositoryService/GarbageCollect"
# max_per_repo = 1

Uncommenting [git] > bin_path does remove the warning, but Gitaly doesn't give me any indicator as to what's wrong.

How can I find out why the start fails? It does say it's the config, but I can't find the error...