Can't insert PID-file full path in the config file
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
**Burrow version**: 1.2.2 Linux 64-bit
I'm trying to pack burrow in RPM. In the config-file I've changed the pidfile path:
```
[general]
pidfile="/var/run/burrow.pid"
stdout-logfile="/var/log/burrow/burrow.out"
access-control-allow-origin="mysite.example.com"
```
But service failed with next error:
```
Cannot interpret contents of PID file: strconv.Atoi: parsing "": invalid syntaxBurrow failed at October 15, 2019 at 11:29am (UTC)
```
Same error, when I'm trying to run burrow manually:
```
/opt/burrow/burrow --config-dir /etc/burrow/
Reading configuration from /etc/burrow/
Cannot interpret contents of PID file: strconv.Atoi: parsing "": invalid syntaxBurrow failed at October 15, 2019 at 11:34am (UTC)
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with the shown /etc/burrow configuration and the --config-dir entry point, then trace how the configured PID-file path is read. Done means Burrow accepts the full PID-file path and starts without the empty-value strconv.Atoi error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100