clowder-framework / clowder

A data management system that allows users to share, annotate, organize and analyze large collections of datasets. It provides support for extensible metadata annotation using JSON-LD and a distribute analytics event bus for automatic curation of uploaded data.
https://clowderframework.org/
University of Illinois/NCSA Open Source License
36 stars 17 forks source link

Extractor not coming back after deleting #428

Open longshuicy opened 11 months ago

longshuicy commented 11 months ago

Describe the bug After deleting the extractors in the GUI, even though heartbeat shows the extractor is still alive, they do not come back. Mongodb entry disappeared. See those logs but not sure if they are related

023-10-20 10:59:16,534 - [ERROR ] - application - Failed to submit event sink message
com.rabbitmq.client.AlreadyClosedException: clean connection shutdown; reason: Attempt to use closed connection
at com.rabbitmq.client.impl.AMQConnection.ensureIsOpen(AMQConnection.java:161) ~[com.rabbitmq.amqp-client-3.0.0.jar:na]
at com.rabbitmq.client.impl.AMQConnection.createChannel(AMQConnection.java:470) ~[com.rabbitmq.amqp-client-3.0.0.jar:na]
at services.RabbitMQMessageService.submit(RabbitMQMessageService.scala:241) ~[clowder.clowder-1.22.0.jar:1.22.0]
at services.EventSinkService.logEvent(EventSinkService.scala:37) [clowder.clowder-1.22.0.jar:1.22.0]
at services.EventSinkService.logFileViewEvent(EventSinkService.scala:83) [clowder.clowder-1.22.0.jar:1.22.0]
at controllers.Files$$anonfun$file$1.apply(Files.scala:281) [clowder.clowder-1.22.0.jar:1.22.0

To Reproduce Steps to reproduce the behavior:

  1. Go to extractor cateolog

    image
  2. Click on "Delete"

  3. Wait for x amount of time depends on your heartbeat setting (usually 5 minutes)

Expected behavior Those extractors that you deleted never come back