logstash exits automatically

189 views
Skip to first unread message

nutun

unread,
Oct 14, 2019, 12:24:03 AM10/14/19
to dcm4che
Hi,

I have deployed dcm4chee-arc-psql:5.19.0-secure (dockerized) in Debian OS. I have an issue that "logstash" exits automatically. Logstash version is 7.2.0-9. Logs are as follow:

2019-10-14 09:06:55,563 INFO  [org.dcm4che3.net.Connection] (EE-ManagedScheduledExecutorService-default-Thread-6) Initiate connection from /0.0.0.0:0 to logstash:8514
2019-10-14 09:06:55,563 WARN  [org.dcm4chee.arc.audit.AuditService] (EE-ManagedScheduledExecutorService-default-Thread-6) Failed to emit audit message for [AuditLogger=Audit Logger]
: java.net.UnknownHostException: logstash
        at java.base/java.net.InetAddress$CachedAddresses.get(InetAddress.java:798)
        at java.base/java.net.InetAddress.getAllByName0(InetAddress.java:1489)
        at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1348)
        at java.base/java.net.InetAddress.getAllByName(InetAddress.java:1282)
        at java.base/java.net.InetAddress.getByName(InetAddress.java:1232)
        at org.dcm...@5.19.0//org.dcm4che3.net.Connection.hostAddr(Connection.java:814)
        at org.dcm...@5.19.0//org.dcm4che3.net.Connection.getEndPoint(Connection.java:854)
        at org.dcm...@5.19.0//org.dcm4che3.net.Connection.connect(Connection.java:969)
        at org.dcm4ch...@5.19.0//org.dcm4che3.net.audit.AuditLogger$TCPConnection.connect(AuditLogger.java:1175)
        at org.dcm4ch...@5.19.0//org.dcm4che3.net.audit.AuditLogger$TCPConnection.sendMessage(AuditLogger.java:1184)
        at org.dcm4ch...@5.19.0//org.dcm4che3.net.audit.AuditLogger.sendMessage(AuditLogger.java:754)
        at org.dcm4ch...@5.19.0//org.dcm4che3.net.audit.AuditLogger.write(AuditLogger.java:730)
        at deployment.dcm4chee-arc-ear-5.19.0-psql-secure.ear//org.dcm4chee.arc.audit.AuditService.emitAuditMessage(AuditService.java:967)
        at deployment.dcm4chee-arc-ear-5.19.0-psql-secure.ear//org.dcm4chee.arc.audit.AuditService.auditConnectionFailure(AuditService.java:303)
        at deployment.dcm4chee-arc-ear-5.19.0-psql-secure.ear//org.dcm4chee.arc.audit.AuditService.aggregateAuditMessage(AuditService.java:119)
        at deployment.dcm4chee-arc-ear-5.19.0-psql-secure.ear//org.dcm4chee.arc.audit.AuditService.auditAndProcessFile(AuditService.java:369)
        at jdk.internal.reflect.GeneratedMethodAccessor124.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:567)
        at org.jboss...@3.1.2.Final//org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:38)
        at org.jboss...@3.1.2.Final//org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:106)
        at deployment.dcm4chee-arc-ear-5.19.0-psql-secure.ear//org.dcm4chee.arc.audit.AuditService$Proxy$_$$_WeldClientProxy.auditAndProcessFile(Unknown Source)
        at deployment.dcm4chee-arc-ear-5.19.0-psql-secure.ear//org.dcm4chee.arc.audit.AuditScheduler.execute(AuditScheduler.java:115)
        at deployment.dcm4chee-arc-ear-5.19.0-psql-secure.ear.dcm4chee-arc-service-5.19.0.jar//org.dcm4chee.arc.Scheduler.run(Scheduler.java:78)
        at org.jbo...@18.0.0.Final//org.jboss.as.ee.concurrent.ControlPointUtils$ControlledScheduledRunnable.run(ControlPointUtils.java:158)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
        at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383)
        at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:830)
        at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)

 
Needs guidance to solve this issue.

Gunter Zeilinger

unread,
Oct 14, 2019, 2:03:50 AM10/14/19
to dcm...@googlegroups.com


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

nutun

unread,
Oct 14, 2019, 8:10:58 AM10/14/19
to dcm4che
Hi Gunterze,

Thank you for your response.
During installation I have followed the steps given in this link but I am still facing same problem. All services runs properly but as any data sent to PACS server, data archives successfully but logstash service exits.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm...@googlegroups.com.

Gunter Zeilinger

unread,
Oct 14, 2019, 8:51:23 AM10/14/19
to dcm...@googlegroups.com
What shows the log of logstash accessible by
$ docker-compose logs logstash
or
$ docker logs <logstash-container-id-or-name>
?


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

nutun

unread,
Oct 14, 2019, 11:38:14 PM10/14/19
to dcm4che

I have attached logstash log file.
logstash logs.txt

Gunter Zeilinger

unread,
Oct 15, 2019, 3:03:00 AM10/15/19
to dcm...@googlegroups.com
[2019-10-14T13:19:07,796][ERROR][org.logstash.execution.WorkerLoop] Exception in pipelineworker, the pipeline stopped processing new events, please check your filter configuration and restart Logstash.
org.jruby.exceptions.SystemCallError: (EISDIR) Is a directory - /usr/share/logstash/data/filter-hashtree

Seems you mapped a directory, and not a file to /usr/share/logstash/data/filter-hashtree .


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

nutun

unread,
Oct 15, 2019, 5:13:29 AM10/15/19
to dcm4che
Thank you for your reply.

I have created file named "filter-hashtree" in /usr/share/logstash/data/ and set permissions "chown 1000:1000 /usr/share/logstash/data/". Then dropped the logstash container and re-deployed the logstast container but the problem is still there.
I am attaching log file. Please guide me if I am missing something and if there is any change required in configurations etc. 
logstash logs - 01.txt

Gunter Zeilinger

unread,
Oct 15, 2019, 6:03:48 AM10/15/19
to dcm...@googlegroups.com
Recheck you mapping. E.g.:

$ grep -B3 filter-hashtree docker-compose.yml
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /etc/timezone:/etc/timezone:ro
      - /var/local/dcm4chee-arc/logstash/filter-hashtree:/usr/share/logstash/data/filter-hashtree

$ sudo touch /var/local/dcm4chee-arc/logstash/filter-hashtree
$ sudo chown 1000:1000 /var/local/dcm4chee-arc/logstash/filter-hashtree


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

nutun

unread,
Oct 16, 2019, 8:14:04 AM10/16/19
to dcm...@googlegroups.com
Thank you Gunterze for your guideline.
Problem is solved. I have done the following.

- created file in /var/local/dcm4chee-arc/logstash/ named "filter-hashtree" ($ touch /var/local/dcm4chee-arc/logstash/filter-hashtree)
- set permissions to filter-hashtree file ($ chown1000:1000 /var/local/dcm4chee-arc/logstash/filter-hashtree)

- created directory "logstash" in /usr/share/data/ ($ mkdir -p /usr/share/data/logstash)
- set permissions to logstash ($ chown 1000:1000 /usr/share/data/logstash)

- created file in  /usr/share/data/logstash/ named "filter-hashtree" ($ touch /usr/share/data/logstash/filter-hashtree)
- set permissions to filter-hashtree file ($ chown 1000:1000 /usr/share/data/logstash/filter-hashtree)

Previously "filter-hashtree" was created as directory and I replaced that directory as file.

LeoGut

unread,
Oct 16, 2019, 9:25:21 AM10/16/19
to dcm4che
Thanks to both of you nutun and gunterze, I had this issue and have been trying to solve it for a few months now and was eager to see the solution... I also believed the filter-hashtree was supposed to be a directory, not a file.
I advise to add the following lines in bold to the wiki installation instructions:

$ sudo mkdir -p /var/local/dcm4chee-arc/logstash
$ sudo chown 1000:1000 /var/local/dcm4chee-arc/logstash
$ sudo touch /var/local/dcm4chee-arc/logstash/filter-hashtree
$ sudo chown 1000:1000 /var/local/dcm4chee-arc/logstash/filter-hashtree

Just these 2 new lines solved my issue.
Thanks again!

Gunter Zeilinger

unread,
Oct 16, 2019, 10:10:38 AM10/16/19
to dcm...@googlegroups.com


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

Reply all
Reply to author
Forward
0 new messages