[
http://mifosforge.jira.com/browse/MIFOSADMIN-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Shah resolved MIFOSADMIN-305.
-----------------------------------
Resolution: Fixed
bounced the confluence server, root cause could not be determined
> confluence.mifos.org down
> -------------------------
>
> Key: MIFOSADMIN-305
> URL: http://mifosforge.jira.com/browse/MIFOSADMIN-305
> Project: mifos administration
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Sumit Shah
> Assignee: Sumit Shah
> Priority: Blocker
> Fix For: Cloud Release A - Iteration 5
>
>
> http://confluence.mifos.org/errors.jsp , seeing this:
> You cannot access Confluence at present. Look at the table below to identify
> the reasons
> Time Level Type Description Exception
> 2011-02-06 00:02:59 (EventLevel: fatal) (EventType: cluster)
> Database is being updated by an instance which is not part of the current
> cluster. You should check network connections between cluster nodes,
> especially multicast traffic.
> Unable to login to shell
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
