it might be a missing JAVA_HOME environment variable? The wrapper probably doesn't use Java to stop it.
- Brett On 17/01/2008, Ben Lidgey <[EMAIL PROTECTED]> wrote: > > We need to stop/start Archiva overnight to allow for backups etc. The cron to > stop it seems to work OK, but when trying to start Archiva from a cron job we > get the following in the wrapper*.log and it fails to start: > > STATUS | wrapper | 2008/01/17 06:00:01 | --> Wrapper Started as Daemon > STATUS | wrapper | 2008/01/17 06:00:01 | Launching a JVM... > ERROR | wrapper | 2008/01/17 06:00:01 | Unable to start JVM: No such file > or directory (2) > ERROR | wrapper | 2008/01/17 06:00:01 | Unable to start a JVM > STATUS | wrapper | 2008/01/17 06:00:01 | <-- Wrapper Stopped > > The crontab for the user under which Archiva is run is > > 00 20 * * * > /home/devadmin/Tools/apache-archiva-1.0/bin/linux-x86-32/run.sh stop > > /home/devadmin/Tools/archiva_stop.log > 00 06 * * * > /home/devadmin/Tools/apache-archiva-1.0/bin/linux-x86-32/run.sh start > > /home/devadmin/Tools/archiva_start.log > > I am stumped to see why the stop works, but the start doesn't. Does anyone > have any ideas or ideas on how I can get more info in the wrapper*.log file > to see what file/directory cannot be found? > > Ben Lidgey > Senior Software Engineer > e: [EMAIL PROTECTED] > > Inuk Networks Limited > Enterprise House > Navigation Park > Abercynon > CF45 4SN > t: +44 (0)844 546 0100 > f: +44 (0)844 546 0200 > w: www.inuknetworks.com > > > This e-mail is confidential and intended solely for the use of the > individual(s) to whom it is addressed. Any views or opinions expressed are > those of the author. If you are not the intended recipient, please be advised > that any use, dissemination, printing or copying of this email is strictly > prohibited. > > -- Brett Porter Blog: http://www.devzuz.org/blogs/bporter/
