Seite 1 von 1

opsi timeout error

Verfasst: 31 Mär 2016, 20:58
von heinzer
Hallo liebe Opsi Fans,

Windows 10, Opsi Client Agent 4.0.6.3.-7, dns läuft

ich habe das Problem, dass Software wieder "verschwindet". Wenn ich etwa 7zip starten möchte, das ich schon öfter benutzen konnte, nachdem ich es erfolgreich mit Opsi installiert hatte, "heult" windows rum, und frägt, ob er die Verknüpfung löschen soll, da ja das Programm weg sei. Und tatsächlich, im 7zip installationsverzeichnis gibts keine Dateien mehr, außer einer: 7zip.dll.

In Opsi kommt dieser Fehler (im configed und wenn ich 7zip per rechte Maustaste und "jetzt on demand ausführen" neu installieren möchte):
opsi timeout error. Timed out after 15 Seconds (last error:[Errno 103] Software caused connection abort)

was kann ich tun?

Vielen Dank und Grüße

Stefan

Re: opsi timeout error

Verfasst: 31 Mär 2016, 21:10
von heinzer
hat sich glaub ich erledigt, der opsi dienst auf dem cleint ist nicht gestartet :) :D

Re: opsi timeout error

Verfasst: 01 Apr 2016, 12:30
von heinzer
doch nicht erledigt, nach einem Neustart ist der Dienst immer noch nich gestartet.
Woran könnte es liegen?

Re: opsi timeout error

Verfasst: 01 Apr 2016, 13:13
von heinzer
habe jetzt neu installiert, der dienst startet wieder , aber es fehlen (immer) Programme - wie kann es sein, dass diese einfach so "verschwinden"?
Wenn ich sie nochmals installiere (über opsiconfigd), sind sie wieder da. :)

liebe Grüße Stefan

Re: opsi timeout error

Verfasst: 01 Apr 2016, 14:03
von n.wenselowski
Hi,

was sagt das opsiclientd.log?

Und was meinst du mit es fehlen Programme?


Gruß

Niko

Re: opsi timeout error

Verfasst: 01 Apr 2016, 23:35
von heinzer
Hallo Nico,

also z.B. 7zip oder calibre ist nicht mehr installiert, ich weiß nicht wie es anders ausdrücken soll - einfach deinstalliert...

Re: opsi timeout error

Verfasst: 04 Apr 2016, 09:27
von n.wenselowski
Hi,
n.wenselowski hat geschrieben:was sagt das opsiclientd.log?
Programme deinstallieren sich ja selten selbst.
Wäre jetzt die Frage, ob die Deinstallation per opsi angestoßen wurde oder durch jemand anderen.


Gruß

Niko

Re: opsi timeout error

Verfasst: 05 Apr 2016, 23:16
von heinzer
[6] [Mar 31 21:03:56:618] JSON Bench for backend_info "params":[],"id":1} Start: 21:01:49:408 Time: 00:02:07:210
[3] [Mar 31 21:03:56:618] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:03:56:618] Problem getting backend_info from service
[6] [Mar 31 21:03:56:618] opsidata not connected - retry
[6] [Mar 31 21:06:04:874] JSON Bench for backend_info "params":[],"id":1} Start: 21:03:57:618 Time: 00:02:07:256
[3] [Mar 31 21:06:04:874] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:06:04:874] Problem getting backend_info from service
[6] [Mar 31 21:06:04:874] opsidata not connected - retry
[6] [Mar 31 21:08:13:130] JSON Bench for backend_info "params":[],"id":1} Start: 21:06:05:874 Time: 00:02:07:256
[3] [Mar 31 21:08:13:130] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:08:13:130] Problem getting backend_info from service
[6] [Mar 31 21:08:13:130] opsidata not connected - retry
[6] [Mar 31 21:10:21:386] JSON Bench for backend_info "params":[],"id":1} Start: 21:08:14:130 Time: 00:02:07:256
[3] [Mar 31 21:10:21:386] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:10:21:386] Problem getting backend_info from service
[6] [Mar 31 21:10:21:386] opsidata not connected - retry
[6] [Mar 31 21:12:29:642] JSON Bench for backend_info "params":[],"id":1} Start: 21:10:22:386 Time: 00:02:07:256
[3] [Mar 31 21:12:29:642] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:12:29:642] Problem getting backend_info from service
[6] [Mar 31 21:12:29:642] opsidata not connected - retry
[6] [Mar 31 21:14:37:898] JSON Bench for backend_info "params":[],"id":1} Start: 21:12:30:642 Time: 00:02:07:256
[3] [Mar 31 21:14:37:898] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:14:37:898] Problem getting backend_info from service
[6] [Mar 31 21:14:37:898] opsidata not connected - retry
[6] [Mar 31 21:16:46:154] JSON Bench for backend_info "params":[],"id":1} Start: 21:14:38:898 Time: 00:02:07:256
[3] [Mar 31 21:16:46:154] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:16:46:154] Problem getting backend_info from service
[6] [Mar 31 21:16:46:154] opsidata not connected - retry
[6] [Mar 31 21:18:54:410] JSON Bench for backend_info "params":[],"id":1} Start: 21:16:47:154 Time: 00:02:07:256
[3] [Mar 31 21:18:54:410] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:18:54:410] Problem getting backend_info from service
[6] [Mar 31 21:18:54:410] opsidata not connected - retry
[6] [Mar 31 21:21:02:666] JSON Bench for backend_info "params":[],"id":1} Start: 21:18:55:410 Time: 00:02:07:256
[3] [Mar 31 21:21:02:666] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:21:02:666] Problem getting backend_info from service
[6] [Mar 31 21:21:02:666] opsidata not connected - retry
[6] [Mar 31 21:23:10:922] JSON Bench for backend_info "params":[],"id":1} Start: 21:21:03:666 Time: 00:02:07:256
[3] [Mar 31 21:23:10:922] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:23:10:922] Problem getting backend_info from service
[6] [Mar 31 21:23:10:922] opsidata not connected - retry
[6] [Mar 31 21:25:19:178] JSON Bench for backend_info "params":[],"id":1} Start: 21:23:11:922 Time: 00:02:07:256
[3] [Mar 31 21:25:19:178] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:25:19:178] Problem getting backend_info from service
[6] [Mar 31 21:25:19:178] opsidata not connected - retry
[6] [Mar 31 21:27:27:434] JSON Bench for backend_info "params":[],"id":1} Start: 21:25:20:178 Time: 00:02:07:256
[3] [Mar 31 21:27:27:434] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:27:27:434] Problem getting backend_info from service
[6] [Mar 31 21:27:27:434] opsidata not connected - retry
[6] [Mar 31 21:29:35:690] JSON Bench for backend_info "params":[],"id":1} Start: 21:27:28:434 Time: 00:02:07:256
[3] [Mar 31 21:29:35:690] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:29:35:690] Problem getting backend_info from service
[6] [Mar 31 21:29:35:690] opsidata not connected - retry
[6] [Mar 31 21:31:43:946] JSON Bench for backend_info "params":[],"id":1} Start: 21:29:36:690 Time: 00:02:07:256
[3] [Mar 31 21:31:43:946] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:31:43:946] Problem getting backend_info from service
[6] [Mar 31 21:31:43:946] opsidata not connected - retry
[6] [Mar 31 21:33:52:202] JSON Bench for backend_info "params":[],"id":1} Start: 21:31:44:946 Time: 00:02:07:256
[3] [Mar 31 21:33:52:202] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:33:52:202] Problem getting backend_info from service
[6] [Mar 31 21:33:52:202] opsidata not connected - retry
[6] [Mar 31 21:36:00:458] JSON Bench for backend_info "params":[],"id":1} Start: 21:33:53:202 Time: 00:02:07:256
[3] [Mar 31 21:36:00:458] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:36:00:458] Problem getting backend_info from service
[6] [Mar 31 21:36:00:458] opsidata not connected - retry
[6] [Mar 31 21:38:08:714] JSON Bench for backend_info "params":[],"id":1} Start: 21:36:01:458 Time: 00:02:07:256
[3] [Mar 31 21:38:08:714] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:38:08:714] Problem getting backend_info from service
[6] [Mar 31 21:38:08:714] opsidata not connected - retry
[6] [Mar 31 21:40:16:970] JSON Bench for backend_info "params":[],"id":1} Start: 21:38:09:714 Time: 00:02:07:256
[3] [Mar 31 21:40:16:970] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:40:16:970] Problem getting backend_info from service
[6] [Mar 31 21:40:16:970] opsidata not connected - retry
[6] [Mar 31 21:42:25:226] JSON Bench for backend_info "params":[],"id":1} Start: 21:40:17:970 Time: 00:02:07:256
[3] [Mar 31 21:42:25:226] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:42:25:226] Problem getting backend_info from service
[6] [Mar 31 21:42:25:226] opsidata not connected - retry
[6] [Mar 31 21:44:33:482] JSON Bench for backend_info "params":[],"id":1} Start: 21:42:26:226 Time: 00:02:07:256
[3] [Mar 31 21:44:33:482] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:44:33:482] Problem getting backend_info from service
[6] [Mar 31 21:44:33:482] opsidata not connected - retry
[6] [Mar 31 21:46:41:738] JSON Bench for backend_info "params":[],"id":1} Start: 21:44:34:482 Time: 00:02:07:256
[3] [Mar 31 21:46:41:738] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:46:41:738] Problem getting backend_info from service
[6] [Mar 31 21:46:41:738] opsidata not connected - retry
[6] [Mar 31 21:48:49:994] JSON Bench for backend_info "params":[],"id":1} Start: 21:46:42:738 Time: 00:02:07:256
[3] [Mar 31 21:48:49:994] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:48:49:994] Problem getting backend_info from service
[6] [Mar 31 21:48:49:994] opsidata not connected - retry
[6] [Mar 31 21:50:58:250] JSON Bench for backend_info "params":[],"id":1} Start: 21:48:50:994 Time: 00:02:07:256
[3] [Mar 31 21:50:58:250] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:50:58:250] Problem getting backend_info from service
[6] [Mar 31 21:50:58:250] opsidata not connected - retry
[6] [Mar 31 21:53:06:506] JSON Bench for backend_info "params":[],"id":1} Start: 21:50:59:250 Time: 00:02:07:256
[3] [Mar 31 21:53:06:506] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:53:06:506] Problem getting backend_info from service
[6] [Mar 31 21:53:06:506] opsidata not connected - retry
[6] [Mar 31 21:55:14:762] JSON Bench for backend_info "params":[],"id":1} Start: 21:53:07:506 Time: 00:02:07:256
[3] [Mar 31 21:55:14:762] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:55:14:762] Problem getting backend_info from service
[6] [Mar 31 21:55:14:762] opsidata not connected - retry
[6] [Mar 31 21:57:23:018] JSON Bench for backend_info "params":[],"id":1} Start: 21:55:15:762 Time: 00:02:07:256
[3] [Mar 31 21:57:23:018] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:57:23:018] Problem getting backend_info from service
[6] [Mar 31 21:57:23:018] opsidata not connected - retry
[6] [Mar 31 21:59:31:274] JSON Bench for backend_info "params":[],"id":1} Start: 21:57:24:018 Time: 00:02:07:256
[3] [Mar 31 21:59:31:274] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 21:59:31:274] Problem getting backend_info from service
[6] [Mar 31 21:59:31:274] opsidata not connected - retry
[6] [Mar 31 22:01:39:530] JSON Bench for backend_info "params":[],"id":1} Start: 21:59:32:274 Time: 00:02:07:256
[3] [Mar 31 22:01:39:530] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 22:01:39:530] Problem getting backend_info from service
[6] [Mar 31 22:01:39:530] opsidata not connected - retry
[6] [Mar 31 22:03:47:786] JSON Bench for backend_info "params":[],"id":1} Start: 22:01:40:530 Time: 00:02:07:256
[3] [Mar 31 22:03:47:786] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 22:03:47:786] Problem getting backend_info from service
[6] [Mar 31 22:03:47:786] opsidata not connected - retry
[6] [Mar 31 22:05:56:042] JSON Bench for backend_info "params":[],"id":1} Start: 22:03:48:786 Time: 00:02:07:256
[3] [Mar 31 22:05:56:042] Error: retrieveJSONObject --- opsi service problem ----> unexpected Result from webservice in retrieveJSONObject, number of lines: 0
[3] [Mar 31 22:05:56:042] Problem getting backend_info from service
[6] [Mar 31 22:05:56:042] opsidata not connected - retry
[3] [Mar 31 22:05:57:042] init connection failed (timeout after 30 seconds/retries.
[3] [Mar 31 22:05:57:042] init failed

Re: opsi timeout error

Verfasst: 06 Apr 2016, 08:05
von m.radtke
uj Logschnipsel.

Es bietet sich an zB. Pastebin zu nutzen um komplette logs zu sichern und zur Verfügung zu stellen ;)

Gruß
Mathias

Re: opsi timeout error

Verfasst: 06 Apr 2016, 12:01
von n.wenselowski
Kontext wäre auch gut.

Ansonsten bitte nicht mehrfach posten.
Und wenn du Hilfe willst, dann solltest du die Fragen auch beantworten.