Geben Sie Ihren Benutzernamen und Ihr Passwort ein.

Passwort vergessen?

Verinice 1.15 und 1.16 Linux Client 32 Bit extreme Perfomance Probleme

Autor Nachricht
Verfasst am: 17. 05. 2018 [09:19]
ralfdamm
Ralf Damm
Themenersteller
Dabei seit: 24.10.2014
Beiträge: 5
Wir haben seit ein paar Wochen extreme Perfomanceprobleme mit Verinice:
- Objekte aufrufen / editieren / speichern
- Export
- Bericht
- Export läuft nun schon 12 Stunden im Hintergrund

Umgebung: CENTOS 6.9

Die Dauerfehlermeldung ist:

2018-05-17 09:07:56,386 ERROR [pool-5614-thread-1] (TreeElementDao.java:279) - Error while updating index, element: ea62871b-37fb-4839-9a67-849235201760
org.elasticsearch.action.UnavailableShardsException: [verinice][1] [1] shardIt, [0] active : Timeout waiting for [1m], request: org.elasticsearch.action.update.UpdateRequest@1e70aaa
at org.elasticsearch.action.support.single.instance.TransportInstanceSingleOperationAction$AsyncSingleAction$3.onTimeout(TransportInstanceSingleOperationAction.java:272)
at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:239)
at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:497)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:74icon_cool.gif
2018-05-17 09:07:56,403 ERROR [pool-5614-thread-2] (TreeElementDao.java:279) - Error while updating index, element: 145f3fb7-245a-4ea6-b7db-4c269a8bd8d6
org.elasticsearch.action.UnavailableShardsException: [verinice][1] [1] shardIt, [0] active : Timeout waiting for [1m], request: org.elasticsearch.action.update.UpdateRequest@1cfb764
at org.elasticsearch.action.support.single.instance.TransportInstanceSingleOperationAction$AsyncSingleAction$3.onTimeout(TransportInstanceSingleOperationAction.java:272)
at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:239)
at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:497)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:74icon_cool.gif
2018-05-17 09:07:56,403 ERROR [pool-5614-thread-3] (TreeElementDao.java:279) - Error while updating index, element: 32a3ff8c-6469-40ea-abc7-3d33efc98b66
org.elasticsearch.action.UnavailableShardsException: [verinice][1] [1] shardIt, [0] active : Timeout waiting for [1m], request: org.elasticsearch.action.update.UpdateRequest@443f56
at org.elasticsearch.action.support.single.instance.TransportInstanceSingleOperationAction$AsyncSingleAction$3.onTimeout(TransportInstanceSingleOperationAction.java:272)
at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:239)
at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:497)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:74icon_cool.gif

und in der .log
!ENTRY org.eclipse.ui 4 0 2018-05-16 17:35:37.612
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?))
at org.eclipse.swt.SWT.error(SWT.java:4282)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:13icon_cool.gif
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:66icon_cool.gif
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at sernet.gs.ui.rcp.main.Application.start(Application.java:4icon_cool.gif
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:49icon_cool.gif
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
Caused by: java.lang.IllegalStateException: Need an underlying widget to be able to set the input.(Has the widget been disposed?)
at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1681)
at sernet.gs.ui.rcp.main.bsi.editors.ReloadLinksWorkspaceJob$1.run(ReloadLinksWorkspaceJob.java:70)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)


Über einen Tip vom Verinice - Team hierzu würden wir uns sehr freuen.
Kann man die Datenbank reorganisieren?

Wir wünschen allen auch schöne Pfingsten.
Verfasst am: 26. 10. 2018 [07:56]
mairo
MM
Dabei seit: 05.01.2017
Beiträge: 6
Hallo Herr Damm,
habe ähnliche Probleme, gab es bei Ihnen eine Lösung?
Ein schönes Wochenende
Mario M
Verfasst am: 26. 10. 2018 [09:09]
ralfdamm
Ralf Damm
Themenersteller
Dabei seit: 24.10.2014
Beiträge: 5
"mairo" wrote:

Hallo Herr Damm,
habe ähnliche Probleme, gab es bei Ihnen eine Lösung?
Ein schönes Wochenende
Mario M


Hallo Mario M.,

Keine Reaktion seitens des Herstellers bis zum heutigen Datum.
Habe die Datenbank über Export und Reimport optimiert.
War ein mühevoller und Verlustreicher Prozess und ich bin mir nicht
sicher, ob der Fehler nicht morgen wieder auftritt (Mulmiges Gefühl).
Ebenso Schönes Wochenende.



English languageDeutsche SpracheLingua italiana
© SerNet GmbH, 2018