Project

General

Profile

Actions

bug #7537

closed

Taxeditor can not connect to restarted, added cdm instance

Added by Andreas Kohlbecker about 6 years ago. Updated almost 6 years ago.

Status:
Rejected
Priority:
New
Category:
taxeditor
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
normal
Found in Version:

Description

After adding and starting, stopping and restarting the new cdn-server instance cdm_phycobank_production on edit test, I can not connect to this instance since the "Connect"-button is greyed out:

Even after updating the Editor to the latest nightly build the problem persists.


Files

picture321-1.png (44.5 KB) picture321-1.png Andreas Kohlbecker, 07/09/2018 03:36 PM
Actions #1

Updated by Andreas Müller almost 6 years ago

  • Assignee changed from Andreas Müller to Katja Luther
  • Target version changed from Unassigned CDM tickets to Release 5.2

Not sure if this is really a taxeditor ticket. However, we should test (and fix it soon).

KL/PP can you please decide who will do it. If it is a CDM server issue, please pass to AK.

Actions #2

Updated by Patrick Plitzner almost 6 years ago

  • Status changed from New to Feedback
  • Assignee changed from Katja Luther to Andreas Kohlbecker

Is this still an issue? The "Connect" button is not greyed out for me. I could also log in.

Actions #3

Updated by Andreas Kohlbecker almost 6 years ago

  • Assignee changed from Andreas Kohlbecker to Patrick Plitzner

You need to add a new cdm-remote instance to a cdmserver start only this instance and then try to connect the Taxeditor to it.
This instance is listed in the select but the connect button stays grey. This is what I observed.

Please test again if you where not adding a new instance in order to reproduce this issue.

Actions #4

Updated by Patrick Plitzner almost 6 years ago

  • Assignee changed from Patrick Plitzner to Andreas Kohlbecker
  1. I commented the campanula DB
  2. Restarted the cdmserver
  3. Tried to connect to instances that were already up during startup -> worked fine
  4. When all instances were up I tried to connect again to already up instances -> works fine
  5. Hit "Reload configuration" -> Connect with previously commented campanula DB -> works fine
Actions #5

Updated by Andreas Kohlbecker almost 6 years ago

  • Status changed from Feedback to Rejected

OK, it seems as this is not reproducible. I am closing the issue as rejected.

Actions #6

Updated by Andreas Müller almost 6 years ago

  • Target version deleted (Release 5.2)
Actions

Also available in: Atom PDF