Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Message-ID: <27603713.227561292895900758.JavaMail.jira@thor>
Date: Mon, 20 Dec 2010 20:45:00 -0500 (EST)
From: "David Crossley (JIRA)" <jira@apache.org>
To: dev@forrest.apache.org
Subject: [jira] Commented: (FOR-1209) on our new zones server the forrest
 installation is not updating itself
In-Reply-To: <22419872.130331292393820926.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FOR-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973444#action_12973444 ] 

David Crossley commented on FOR-1209:
-------------------------------------

Gav found the reason, See r1051093. Minimal shell, so needed full path to 'svn' etc.

This worked on the old zone server because all of its forrest cronjob scripts source our "setenv.sh' script. This set the $PATH appropriately. However that was commented out on the new zone server.

I will fix the other cronjobs to use full pathnames.

> on our new zones server the forrest installation is not updating itself
> -----------------------------------------------------------------------
>
>                 Key: FOR-1209
>                 URL: https://issues.apache.org/jira/browse/FOR-1209
>             Project: Forrest
>          Issue Type: Bug
>          Components: zones.a.o administration
>            Reporter: David Crossley
>            Assignee: David Crossley
>
> I noticed that the "seed-sample" site was not reflecting recent changes. On the server, there are no logfiles in ~forrest/config/ from the "update-forrest-trunk" job. The crontab seems okay.
> Running the script "update_check.sh" manually, did work and did svn updates (it seems for previous 7 weeks or so), and re-built forrest as it should.
> So i don't know why not running from cron. (The actual forrestbot jobs are running properly via cron.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.