[TD-82] ERROR: Failed to create organization 'Public'

[taskwarrior]

Loren Rogers on 2014-12-07T04:41:07Z says:

I can't get taskd to add an org. I can configure taskd, but it won't create an org or user. Is there a way to get more useful diagnostics for this step? Seems like a permissions issue in my setup, but I'm not sure where.

me(at)server:/var$ taskd add org 'Public'
ERROR: Failed to create organization 'Public'.

[taskwarrior]

Migrated metadata:

Created: 2014-12-07T04:41:07Z
Modified: 2016-09-02T20:02:38Z

[taskwarrior]

Loren Rogers on 2014-12-07T05:11:47Z says:

This may have just been a n00b issue -- I re-did the setup as root, and was able to create the org. Perhaps the manual should point this out / the error should have more details?

[taskwarrior]

Paul Beckingham on 2014-12-10T23:42:45Z says:

A note was added to the configuration documentation that the user running the server must have write permission in the chosen directory.

[taskwarrior]

Onion on 2016-03-11T18:30:06Z says:

I had the same problem and found, that - even though my $TASKDDATA points to /var/taskd/config , all configuration values were written into a file "taskd" directly in my home folder. So I tried over and over again several write permissions of the wrong file, until I found out what's going on today.

[taskwarrior]

Benoit Grégoire on 2016-09-02T16:55:35Z says:

Another possible cause (especially likely if you use the debian/ubuntu packages), it that the orgs subdirectory does not exits while the config file does. Especially baffling since all your previous tasd config set commands worked fine.

To fix it, mkdir $TASKDDATA/orgs

(and check the premissions on that directory)

[taskwarrior]

Paul Beckingham on 2016-09-02T18:20:55Z says:

The 'orgs' directory is created by the 'taskd init' command. Either the init command is not being run (i.e. not following instructions) or the binary package installed does a half-assed job of setup. Either way, I don't think this is a problem in the code.

[taskwarrior]

Benoit Grégoire on 2016-09-02T19:48:51Z says:

It's the second case (binary package installed does a half-assed job of setup). I did not re-open the ticket ;)

But as this is literally the only place where the error message is found on google, the symptoms are the same, and (frankly) the error message is unhelpful, I thought it was worth documenting here.

[taskwarrior]

Paul Beckingham on 2016-09-02T20:02:38Z says:

... and thanks for doing that. Much appreciated.