Added in ARCHIVA_BASE. I see no sign of appserver.base in the output of the startup script. I made /opt/archiva/logs writable by the archiva user and it placed a pid file in that directory. The startup script just seems to be ignoring ARCHIVA_BASE entirely. I'll try the puppet module again with the stripped down configuration.
On Tue, Jun 24, 2014 at 4:45 PM, Joseph Wilkicki <[email protected]> wrote: > My mailing list subscription is a little messed up, but this is in reply > to this message: > > > http://mail-archives.apache.org/mod_mbox/archiva-users/201406.mbox/%3CDE946284-8A9F-4919-9D17-B1683B1700F7%40apache.org%3E > > I'll try adding ARCHIVA_BASE directly to the init script and see if that > helps. > > I had mentioned Puppet rules in my original mail. I meant the puppet > module mentioned in Brent's reply: maestrodev/archiva I tried to use > the LDAP parameters and the external user JDBC from the module > documentation (which was only in init.pp and not in the README.md on Puppet > Forge) and neither worked successfully. I assume the former didn't work > because 2.0.1 does a graphical setup for LDAP now and I don't really know > why it didn't setup MySQL properly. It seemed no matter what I did, > Archiva couldn't create the guest account or the admin user account even > though the puppetlabs/mysql module setup the database properly. > >
