[jira] Resolved: (INFRA-1002) Confluence need to be started

["Ted Husted (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/INFRA-1002?page=all ]

Ted Husted resolved INFRA-1002.
-------------------------------

    Resolution: Fixed

---------- Forwarded message ----------
From: Don Brown <mr...@apache.org>
Date: Oct 27, 2006 5:10 PM
Subject: Re: Brutus Account for Upayavira (was Re: Confluence admin and maintenece)

Ok, I gave up on the Jetty, and have moved Confluence over to Tomcat,
along side the existing JIRA installations, following their pattern.

Good news - Confluence is back up!  The problem was a bad plugin, html,
which was bringing the whole system down.  The new version of confluence
doesn't let a bad plugin bring it down, so I'm going to upgrade
confluence to 2.2.9 while I'm here.

I'll write up more when I get it all done.

Don

---------- Forwarded message ----------
From: Don Brown <mr...@apache.org>
Date: Oct 27, 2006 7:09 PM
Subject: Confluence status: Upgrade complete, autoexport plugin broken
To: Infrastructure Apache <in...@apache.org>


Good news - the Confluence 2.2.9 update seems to have been successful,
and it is now running on Tomcat along side our JIRA instances.  The details:
 - Home: /usr/local/tomcat/tomcat-confluence
 - Data home: /usr/local/tomcat/tomcat-confluence/var
 - Init script: /etc/init.d/confluence (same name as old)
 - Runs as user 'www-data' like old
 - Patterned off tomcat-jira-struts
 - Ports documented in /usr/local/tomcat/PORTS.txt
 - My backup files (db and war) in
/usr/local/tomcat/tomcat-confluence/backups


I tried to follow the conventions of all the JIRA installations, so
problems will be easier to debug next time.  If there is anything
additional I should document, please speak up.

Bad news - Autoexport plugin isn't compatible with Confluence 2.2.9 and
Tomcat doesn't startup correctly every other time (?!), complaining
about a port already in use that I can't track down.

Does anyone have the source of the autoexport plugin?  I could whip it
into shape this weekend.  As for the startup problem, it has me
stumped.  It seems like such a simple problem, and its driving me crazy
:)  I'll play with it some more this weekend.

Don


---------- Forwarded message ----------
From: Don Brown <mr...@apache.org>
Date: Oct 27, 2006 7:46 PM
Subject: Confluence status: Operational (Autoexport plugin working)
To: Infrastructure Apache <in...@apache.org>


I built and installed version 0.14-dev of the Autoexport plugin, and it
seems to be working correctly.  I'm going to call it a day, so from now
on, Confluence should be considered operational.  Let me know if there
is anything I missed or need to document.

Don


> Confluence need to be started
> -----------------------------
>
>                 Key: INFRA-1002
>                 URL: http://issues.apache.org/jira/browse/INFRA-1002
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Confluence
>            Reporter: Hernan Cunico
>            Priority: Blocker
>
> Confluence has been down since the move to the new data center. Services on brutus have been up since 4 days ago except for Confluence. This is affecting many projects that are using confluence as their wiki.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira