opsiclientd.log wächst bis die HDD voll ist

[Erkstasy]

Guten Morgen zusammen,

vor ca einem Monat hat sich einer unserer Mitarbeiter über zu wenig Festplattenspeicher beschwert. Bei genauerer Betrachtung ist aufgefallen, dass die opsiclientd.log.0 auf über 30GB auf das Limit der Festplatte angewachsen war. Ein einfaches Löschen hat das "Problem" behoben.

Heute Morgen ist das Problem an einem anderen PC aufgetreten. Dort war allerdings die opsiclientd.log direkt betroffen. Löschen führte nicht zum Erfolg, da die Datei direkt wieder erstellt wurde und immer größer wurde. Nach einem Neustart ließ sich die nun logischerweise als opsiclientd.log.0 benannte Datei ohne Weiteres löschen.

Hat einer eine Idee, wo der Fehler liegen könnte?

Gruß
Erik

[ueluekmen]

Hi,

ist jetzt nur eine Vermutung, aber kann es sein, dass diese Rechner im Dauerbetrieb sind?

[Erkstasy]

Nein, normalerweise werden diese zum Feierabend runtergefahren.

[ueluekmen]

Ok, das ist dann komisch. Normalerweise wird das log immer rotated, und zwar immer dann, wenn der opsiclientd neu gestartet wird. Ich würde an der Stelle mal die Info-Page vom Client checken, wielange der opsiclientd gelaufen ist.

Welche Versionen hast du im Einsatz? Opsi und opsi-client-agent?

Die Logs können schon mal größer werden, aber um 30GB log an zu sammeln, muss der Client schon einige Zeit durchlaufen, damit überhaupt soviel zusammenkommt.

[Erkstasy]

Wir arbeiten hier noch mit Version 4.0.3.

Wo steht das genau, wie lange der Client gelaufen ist?

[mhaegele]

Kann es sein daß der Loglevel ziemlich hoch ist?
Bei einem Dauerläufer hier ist das c:\tmp verzeichnis mit allen Logresten auf ca. 40MB angewachsen ...
Es gibt 3 opsiclientd.log opsiclientd.log.1 opsiclientd.log.2 diese sind zusammen ca. 700 KByte
groß für Zeitraum ca. 3 Monate im ältesten Log ...

Der Client läuft oft 1 Monat oder auch mal länger durch je nachdem wann das nächste Opsi Testpaket dort inst. wird ...


hth
MH

[Erkstasy]

So, hab den Thread vollkommen aus den Augen verloren.
Der Loglevel steht auf Standard. Was mich halt wundert ist, dass bei rund 100 Arbeitsstationen bisher nur 3 von denen das Problem hatten.

Mein PC hier hat z.B. nur rund 800kb an logfiles im tmp-Verzeichnis

[n.wenselowski]

Hallo,

schon mal einen Blick in das problematische Log geworfen?
Gibts sich wiederholende Meldungen, die eventuell auf Probleme hinweisen?


Gruß

Niko

[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

[dark alex]

ja da ist irgendwas schiefgelaufen... Bzw läuft schief.

Welche Client-Agent-Version hast du denn?
Ich würde denke ich ein Backup machen und mal rundum updaten...