Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 665748 - dev-util/drone-0.8.6: drone-server won't start because environment variables are not passed on
Summary: dev-util/drone-0.8.6: drone-server won't start because environment variables ...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: William Hubbs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-12 02:09 UTC by tastytea
Modified: 2020-01-08 14:46 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tastytea 2018-09-12 02:09:28 UTC
The variables from /etc/conf.d/drone-server are not passed on to the drone-server.

Reproducible: Always

Steps to Reproduce:
1. Configure drone-server in /etc/conf.d/drone-server
2. Run /etc/init.d/drone-server start
3. Read /var/log/drone-server/drone-server.log
Actual Results:  
drone-server didn't start, logfile reads:
[…] level=fatal msg="DRONE_HOST is not properly configured"

Expected Results:  
drone-server starts, configured with the variables in /etc/conf.d/drone-server.
Comment 1 David 2018-12-31 17:56:42 UTC
(In reply to tastytea from comment #0)
> The variables from /etc/conf.d/drone-server are not passed on to the
> drone-server.
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. Configure drone-server in /etc/conf.d/drone-server
> 2. Run /etc/init.d/drone-server start
> 3. Read /var/log/drone-server/drone-server.log
> Actual Results:  
> drone-server didn't start, logfile reads:
> […] level=fatal msg="DRONE_HOST is not properly configured"
> 
> Expected Results:  
> drone-server starts, configured with the variables in
> /etc/conf.d/drone-server.

I have the same bug. Is there a patch available?
Comment 2 tastytea 2018-12-31 23:07:12 UTC
(In reply to David from comment #1)
> I have the same bug. Is there a patch available?

The only solution I have found is to pass each and every variable to start-stop-daemon, with -e DRONE_HOST="${DRONE_HOST}" -e DRONE_SECRET="${DRONE_SECRET}" and so on.