Just to summarize.
Turned out to be a missing HOME variable when running in automated
mode that caused all the trouble. That variable is used when
initializing the Firefox profile.
Case closed.
-- Ørjan
On Nov 14, 3:21 pm, Orjan <
orjanmje...@yahoo.com> wrote:
> Hi,
>
> I am working on a project where we want to use Selenium in our
> testing. The setup is headless test server running an Bamboo remote
> agent with Xvfb.
>
> The setup is as follows:
> CentOS 6 x86_64
> Atlassian Bamboo
> Maven 2.2.1
> Java 1.6.0_29
> Xvfb 1.7.7
> Selenium 2.10.0Firefox3.6.9
>
> When running the tests through Bamboo we get the following error.
>
> -------------------------------------------------------
> build 14-Nov-2011 14:43:26 T E S T S
> build 14-Nov-2011
> 14:43:26 -------------------------------------------------------
> build 14-Nov-2011 14:43:26 Running SomeITCase
> build 14-Nov-2011 14:43:30 log4j:WARN No appenders could be found for
> logger (org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager).
> build 14-Nov-2011 14:43:30 log4j:WARN Please initialize the log4j
> system properly.
> build 14-Nov-2011 14:44:15
> org.openqa.selenium.firefox.NotConnectedException: Unable to connect
> to host 127.0.0.1 on port 7055 after 45000 ms.Firefoxconsole output:
> Notice themkdirerror - "cannot create directory `/.mozilla'.
> I have tried manually creating this directory (/.mozilla) and
> assigning ownership to the atlassian user but does not seem to make
> any difference...
>
> When running the samme unit tests from command line as atlassian user
> everything works fine. Also when running from command line there is a
> temporaryfirefoxprofiledirectory created under '/tmp'. Ex: /tmp/
> anonymous7645808369331264586webdriver-profile/
> Owner is the atlassian user.
> This directory is _not_ created when running automatically...
>
> Am I correct in guessing that the /.mozilla directory that fails
> creation in the automatic run is the fallbackprofiledirectory that