Cannot (or should not) use root to register ejabberd users

Previous discussion in IRC:
http://irc.evergreen-ils.org/evergreen/2018-12-18#i_388768
http://irc.evergreen-ils.org/evergreen/2019-01-16#i_390935

FWIW, I have never had a problem doing that step with sudo. I install on Ubuntu 16.04 all the time.

I've had a chance to poke at this just in the last few days. It appears there's a difference between systems installed fresh with 16.04 and those upgraded from 14.04. On my fresh install system I can use sudo ejabberdctl ... without any issue, but on my upgraded machine I had to either change the apparmor profile or use sudo -u ejabberd ejabberdctl ... instead.

As an added wrinkle the fresh install was directly on real hardware and the upgrade was a VM on another machine, so there may be more than one variable that contributes to this problem.

Since it seems to keep coming up and is inconsistent it may be worth considering just suggesting using sudo -u to prevent it from being a problem in the future. If we have to make a note in the docs to the effect of "In case you see this go sideways, try this..." we may as well just change the instructions to the method that always works.

The bulk of my experience has been with fresh installations of Ubuntu 16.04 on virtual machines, using libvirt with qemu-kvm. I have never had an issue using sudo with the ejabberdctl steps in that environment.

I did upgrad a VM from Ubuntu 14.04 to 16.04 several years ago, but I don't recall if I had any issues with that step, or if I even performed that step given that the VM already had OpenSRF and Evergreen installed.

Can't edit a comment, so yeah, I tyoped upgrade as "upgrad."

But, I meant to add that I agree with Jason about adding sudo -u ejabberd to the ejabberdctl steps for Ubuntu.

(I don't like typing in web forms, do you?)

Add milestone, plan to resolve alongside other changes to OpenSRF readme for next major series.