On Linux Arch based Manjaro i have edited /etc/tor/torrc and i have un-commented the line:
#Log notice file /var/log/tor/notices.log
and from that time, tor was failing to start and not providing any thrutful message on the reason.

Reason provided was: tor.service: Start request repeated too quickly.

systemctl told me to check "journalctl -xe" but that not shown any detail.
After wasting the time on bug trackers, i have found command journalctl -f
and then ran "systemctl restart tor" command and that recorded details:

[warn] Couldn't open file for 'Log notice file /var/log/tor/notices.log': No such file or directory
[notice] Closing partially-constructed Socks listener connection (ready) on
[notice] Closing partially-constructed Control listener connection (ready) on
[warn] Failed to parse/validate config: Failed to init Log options. See logs for details.
[err] Reading config failed--see warnings above.
systemd[1]: tor.service: Main process exited, code=exited, status=1/FAILURE

The problem was in config file (/etc/tor/torrc)? in my case the line:
#Log notice file /var/log/tor/notices.log
which i have un-commented and it somehow is invalid, despite the "sudo tor --verify-config" not reported any issue.