[Nix-dev] [Fixed?] Re: environment in systemd services

[Arnold Krille]

Hi all,

I kind of fixed it. I played around with the duply config, but that
didn't really change anything.

Then I went back to getting fcron installed and sending emails. And
there I encountered the same problem with the same backtrace with the
empty error message!

So there seems to be something different between the system environment
and roots login shell. So I started not `duply amazon status` but `bash
-l -c "duply amazon status"`, thus running duply in roots login shell.
And now it works! Both when run in cron and when run in its own system
service!

I am not sure if this is the right solution, but at least I got some
backups working now.

As soon as I add backups to a local disk I will check again if duply
can't run with the system environment…

Have fun,

Arnold

On Sat, 30 Jan 2016 14:34:21 +0100 Arnold Krille <arnold at arnoldarts.de>
wrote:
> Nope, the aws credentials are in the url given in the config file.
> 
> I also tried setting serviceConfig with options privateTmp=false and
> privateNetwork=false but these options seem to be for a later version
> of systemd. I am on stock 15.09 here.
> 
> - Arnold
> 
> (Before anyone asks, the backup is encrypted and only the public part
> of the gpg key is present on the server.)
> 
> On Sat, 30 Jan 2016 13:27:52 +0000 zimbatm <zimbatm at zimbatm.com>
> wrote:
> > Did you try to pass the AWS keypair trough an environment
> > variable ? I don't know it that would fix it but it's a 3rd
> > solution, not having access to the right keys.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: not available
Url : http://lists.science.uu.nl/pipermail/nix-dev/attachments/20160130/bcc6f65f/attachment.bin