Folgeaktion bein Once-Script unerwartet

Antworten
mufungu
Beiträge: 5
Registriert: 13 Feb 2013, 13:39

Folgeaktion bein Once-Script unerwartet

Beitrag von mufungu »

Hallo,

wir verwenden eine "Once Script" mit OPSI 4.0.2.4. In der Doku (opsi-getting-started-stable-de.pdf) auf Seite 78 ist beschrieben, dass die Folgeaktion beim Typ "once" "none" sein sollte. Bei uns bleibt aber der Status immer auf "once" stehen, er springt also nach Ausführung nicht auf "none" um. Die Folge ist, dass der Rechner nach jedem Reboot die eingestellte Aktion erneut startet.

Habe ich die Once Aktion falsch verstanden? Ich möchte dass das eingestellte Script nur einmalig ausgeführt wird.

Vielen Dank im voraus

Gruss

Martin
Benutzeravatar
d.oertel
uib-Team
Beiträge: 3319
Registriert: 04 Jun 2008, 14:27

Re: Folgeaktion bein Once-Script unerwartet

Beitrag von d.oertel »

Hi,

das sollte so funktionieren wie Sie es verstanden haben.
Bitte mal die instlog.txt und die dazugehörige log des opsiconfd posten.
Dann sehe ich vielleicht wo es hängt.....

gruß
d.oertel
opsi support - uib gmbh

For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org
mufungu
Beiträge: 5
Registriert: 13 Feb 2013, 13:39

Re: Folgeaktion bein Once-Script unerwartet

Beitrag von mufungu »

Hallo,

habe ich gerade versucht, erhalte aber die Meldung "Das Kontingent für Dateianhänge ist bereits vollständig ausgenutzt.". Als Code einfügen geht nicht, weil ich dann die erlaubte Anzahl an Zeichen überschreite.

Gruss

Martin
mufungu
Beiträge: 5
Registriert: 13 Feb 2013, 13:39

Re: Folgeaktion bein Once-Script unerwartet

Beitrag von mufungu »

instlog.txt

Code: Alles auswählen

[1] [Feb 14 09:59:13:217] opsi-winst 4.11.3.3 started at >>14.02.2013 09:59:10
[1] [Feb 14 09:59:13:217] startmessage opsi-winst created at CentralForm.FormCreate: 14.02.2013 09:59:10
[1] [Feb 14 09:59:13:217] startmessage StartProgramModes and create log: 14.02.2013 09:59:10
[1] [Feb 14 09:59:13:217] startmessage start opsi service connection: 14.02.2013 09:59:10
[1] [Feb 14 09:59:13:217] JSON Bench for backend_info "params":[],"id":1} Start: 09:59:10:921 Time: 00:00:02:294
[1] [Feb 14 09:59:13:217] startmessage create log: 14.02.2013 09:59:13
[6] [Feb 14 09:59:13:218] JSON service request https://192.168.3.5:4447/rpc getDepotId
[6] [Feb 14 09:59:13:375] JSON Bench for getDepotId "params":["opsiclient.noc.unternehmen.de"],"id":1} Start: 09:59:13:218 Time: 00:00:00:157
[6] [Feb 14 09:59:13:380] JSON service request https://192.168.3.5:4447/rpc backend_setOptions
[6] [Feb 14 09:59:13:438] JSON Bench for backend_setOptions "params":[{"processProductOnClientSequence":true}] Start: 09:59:13:380 Time: 00:00:00:058
[6] [Feb 14 09:59:13:445] JSON service request https://192.168.3.5:4447/rpc productOnClient_getObjects
[6] [Feb 14 09:59:13:855] JSON Bench for productOnClient_getObjects "params":["",{"clientId":"opsiclient.noc.unternehmen.d Start: 09:59:13:444 Time: 00:00:00:411
[6] [Feb 14 09:59:13:866] JSON service request https://192.168.3.5:4447/rpc backend_setOptions
[6] [Feb 14 09:59:13:916] JSON Bench for backend_setOptions "params":[{"processProductOnClientSequence":false} Start: 09:59:13:866 Time: 00:00:00:050
[5] [Feb 14 09:59:13:922] Computername:opsiclient.noc.unternehmen.de
[5] [Feb 14 09:59:13:922] Computername according to Environment Variable :OPSICLIENT
[5] [Feb 14 09:59:13:922] opsi service URL https://192.168.3.5:4447
[5] [Feb 14 09:59:13:922] Depot path:  o:\
[5] [Feb 14 09:59:13:922] 
[5] [Feb 14 09:59:13:940] bootmode BKSTD
[5] [Feb 14 09:59:13:940] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[5] [Feb 14 09:59:13:940] Resolved sequence of products (14.02.2013 09:59:13): 
[5] [Feb 14 09:59:13:940] Product 8 	app_check-wsus : once
[5] [Feb 14 09:59:13:940] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[6] [Feb 14 09:59:14:220] JSON service request https://192.168.3.5:4447/rpc getProductProperties_hash
[6] [Feb 14 09:59:14:592] JSON Bench for getProductProperties_hash "params":["app_check-wsus","opsiclient.noc.unternehmen Start: 09:59:14:220 Time: 00:00:00:372
[6] [Feb 14 09:59:14:599] JSON service request https://192.168.3.5:4447/rpc getProduct_hash
[6] [Feb 14 09:59:14:708] JSON Bench for getProduct_hash "params":["app_check-wsus","opsiserver.noc.unternehmen Start: 09:59:14:598 Time: 00:00:00:110
[6] [Feb 14 09:59:14:714] JSON service request https://192.168.3.5:4447/rpc productOnClient_getObjects
[6] [Feb 14 09:59:14:835] JSON Bench for productOnClient_getObjects "params":["",{"clientId":"opsiclient.noc.unternehmen.d Start: 09:59:14:714 Time: 00:00:00:121
[5] [Feb 14 09:59:14:842] scriptname: "check-wsus.ins", special path: "o:\app_check-wsus\"
[1] [Feb 14 09:59:14:861] 
[1] [Feb 14 09:59:14:861] ============ Version 4.11.3.3 WIN32 script "o:\app_check-wsus\check-wsus.ins"
[1] [Feb 14 09:59:14:861]              start: 2013-02-14  09:59:14 
[1] [Feb 14 09:59:14:861]              installing product: app_check-wsus_1.0-1
[1] [Feb 14 09:59:14:861]              on client named    "opsiclient.noc.unternehmen.de"
[1] [Feb 14 09:59:14:861]              loggedin user    ""
[1] [Feb 14 09:59:14:862]              winst running as    "SYSTEM"
[1] [Feb 14 09:59:14:862]              winst running with admin privileges
[1] [Feb 14 09:59:14:862]              winst running in standard script mode
[1] [Feb 14 09:59:14:862] [executing: "C:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-winst\winst32.exe"]
[1] [Feb 14 09:59:14:862] system infos:
[1] [Feb 14 09:59:14:866] 00-50-56-87-02-5F  -  PC hardware address
[1] [Feb 14 09:59:14:866] OPSICLIENT  -  IP name 
[1] [Feb 14 09:59:14:866] 172.20.164.5  -  IP address
[1] [Feb 14 09:59:14:866] DEU  -  System default locale 
[1] [Feb 14 09:59:14:866] MS Windowds 6.1 64 Bit
[1] [Feb 14 09:59:14:866] opsi service version : 4
[1] [Feb 14 09:59:14:866] 
[6] [Feb 14 09:59:14:875] Registry key [HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion]  opened
[6] [Feb 14 09:59:14:875] Key closed
[5] [Feb 14 09:59:15:022] 
[5] [Feb 14 09:59:15:022] Set  $INST_SystemType$ = GetSystemType
[6] [Feb 14 09:59:15:022]   The value of the variable "$INST_SystemType$" is now: "64 Bit System"
[5] [Feb 14 09:59:15:022] 
[5] [Feb 14 09:59:15:022] Execution of DOSBatch_install_updates
[6] [Feb 14 09:59:15:108]   c:\opsi.org\tmp\_winstbat_1.bat saved back
[6] [Feb 14 09:59:15:108]   Executing "cmd.exe" /C "c:\opsi.org\tmp\_winstbat_1.bat"
[6] [Feb 14 10:03:14:143]   ExitCode 10
[6] [Feb 14 10:03:14:153]   Delete "c:\opsi.org\tmp\_winstbat_*"
[6] [Feb 14 10:03:14:153]     Search "c:\opsi.org\tmp\"
[6] [Feb 14 10:03:14:153]     File "c:\opsi.org\tmp\_winstbat_1.bat"
[6] [Feb 14 10:03:14:153]       The file has been deleted
[5] [Feb 14 10:03:14:153]   
[5] [Feb 14 10:03:14:153]   Set  $ExitCode$ = getLastExitCode
[6] [Feb 14 10:03:14:159]     The value of the variable "$ExitCode$" is now: "10"
[5] [Feb 14 10:03:14:160]   Start including tail of LogFile "C:\tmp\wuinstall.log"
[5] [Feb 14 10:03:14:160]   ################################################################
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: WuInstall Version 1.1.
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: Copyright by hs2n Informationstechnologie GmbH 2009-2012
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: This software comes with ABSOLUTELY NO WARRANTY
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: Visit:  http://www.wuinstall.com for more infos, new versions and WuInstallPro 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: FREE VERSION. You are in Domain: WORKGROUP 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: LICENSE INFORMATION: For WuInstall 1.1. this license authorizes for unlimited commercial and non-commercial use.
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: For questions, please contact us under WuInstall@hs2n.at or see http://www.wuinstall.com
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: WuInstallCall: O:\app_check-wsus\bin\WUInstall.exe  /install
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: Your update API: Major Version: 6, Minor Version: 0
[5] [Feb 14 10:03:14:160]   -->: Product Version: 7.5.7601.17514
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: You are using WSUS Server http://sapsus.orga.de
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: Searching for updates ... Criteria: IsInstalled=0 and Type='Software'
[5] [Feb 14 10:03:14:160]   -->: Result Code: Succeeded
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 7 Updates found in total, filtering ...
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 1. Security Update for Windows Server 2008 R2 x64 Edition (KB2790113) 
[5] [Feb 14 10:03:14:160]   -->:  Severity: Important
[5] [Feb 14 10:03:14:160]   -->:  UpdateClassification - Security Updates
[5] [Feb 14 10:03:14:160]   -->:  Product - Windows Server 2008 R2
[5] [Feb 14 10:03:14:160]   -->:  ID: d6f7b5ab-d712-4249-9c8b-597af1eef7ef
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 2. Security Update for Windows Server 2008 R2 x64 Edition (KB2778344) 
[5] [Feb 14 10:03:14:160]   -->:  Severity: Important
[5] [Feb 14 10:03:14:160]   -->:  UpdateClassification - Security Updates
[5] [Feb 14 10:03:14:160]   -->:  Product - Windows Server 2008 R2
[5] [Feb 14 10:03:14:160]   -->:  ID: 1cecc16e-4849-4346-9af1-04e24cc1c164
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 3. Security Update for Windows Server 2008 R2 x64 Edition (KB2790655) 
[5] [Feb 14 10:03:14:160]   -->:  Severity: Important
[5] [Feb 14 10:03:14:160]   -->:  UpdateClassification - Security Updates
[5] [Feb 14 10:03:14:160]   -->:  Product - Windows Server 2008 R2
[5] [Feb 14 10:03:14:160]   -->:  ID: e97051e2-7886-4ead-bb85-ba579e9fb817
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 4. Security Update for Microsoft .NET Framework 4 on XP, Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 for x64 (KB2789642) 
[5] [Feb 14 10:03:14:160]   -->:  Severity: Important
[5] [Feb 14 10:03:14:160]   -->:  UpdateClassification - Security Updates
[5] [Feb 14 10:03:14:160]   -->:  Product - Windows Server 2008 R2
[5] [Feb 14 10:03:14:160]   -->:  ID: 6135bc9c-dc1d-4565-8a53-8b09a4a38c9e
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 5. Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2789645) 
[5] [Feb 14 10:03:14:160]   -->:  Severity: Important
[5] [Feb 14 10:03:14:160]   -->:  UpdateClassification - Security Updates
[5] [Feb 14 10:03:14:160]   -->:  Product - Windows Server 2008 R2
[5] [Feb 14 10:03:14:160]   -->:  ID: 379dcbf4-987b-4305-8709-762ce57b05e6
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 6. Security Update for Windows Server 2008 R2 x64 Edition (KB2799494) 
[5] [Feb 14 10:03:14:160]   -->:  Severity: Important
[5] [Feb 14 10:03:14:160]   -->:  UpdateClassification - Security Updates
[5] [Feb 14 10:03:14:160]   -->:  Product - Windows Server 2008 R2
[5] [Feb 14 10:03:14:160]   -->:  ID: 8c871df8-ba1c-4c50-aa53-e2f3ebc99e69
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 7. Windows Malicious Software Removal Tool x64 - February 2013 (KB890830) 
[5] [Feb 14 10:03:14:160]   -->:  Severity: Unknown
[5] [Feb 14 10:03:14:160]   -->:  UpdateClassification - Update Rollups
[5] [Feb 14 10:03:14:160]   -->:  Product - Windows Server 2008 R2
[5] [Feb 14 10:03:14:160]   -->:  ID: 893dc1b7-895e-4299-a4fd-0fe0ce30118d
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: Downloading updates ...
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 1. Downloading Security Update for Windows Server 2008 R2 x64 Edition (KB2790113):
[5] [Feb 14 10:03:14:160]   -->:  Downloading...
[5] [Feb 14 10:03:14:160]   -->: Downloading finished, checking result ...Result Code: Succeeded
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 2. Downloading Security Update for Windows Server 2008 R2 x64 Edition (KB2778344):
[5] [Feb 14 10:03:14:160]   -->:  Downloading...
[5] [Feb 14 10:03:14:160]   -->: Downloading finished, checking result ...Result Code: Succeeded
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 3. Downloading Security Update for Windows Server 2008 R2 x64 Edition (KB2790655):
[5] [Feb 14 10:03:14:160]   -->:  Downloading...
[5] [Feb 14 10:03:14:160]   -->: Downloading finished, checking result ...Result Code: Succeeded
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 4. Downloading Security Update for Microsoft .NET Framework 4 on XP, Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 for x64 (KB2789642):
[5] [Feb 14 10:03:14:160]   -->:  Downloading...
[5] [Feb 14 10:03:14:160]   -->: Downloading finished, checking result ...Result Code: Succeeded
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 5. Downloading Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2789645):
[5] [Feb 14 10:03:14:160]   -->:  Downloading...
[5] [Feb 14 10:03:14:160]   -->: Downloading finished, checking result ...Result Code: Succeeded
[5] [Feb 14 10:03:14:160]   -->: 
[5] [Feb 14 10:03:14:160]   -->: 6. Downloading Security Update for Windows Server 2008 R2 x64 Edition (KB2799494):
[5] [Feb 14 10:03:14:160]   -->:  Downloading...
[5] [Feb 14 10:03:14:160]   -->: Downloading finished, checking result ...Result Code: Succeeded
[5] [Feb 14 10:03:14:161]   -->: 
[5] [Feb 14 10:03:14:161]   -->: 7. Downloading Windows Malicious Software Removal Tool x64 - February 2013 (KB890830):
[5] [Feb 14 10:03:14:161]   -->:  Downloading...
[5] [Feb 14 10:03:14:161]   -->: Downloading finished, checking result ...Result Code: Succeeded
[5] [Feb 14 10:03:14:161]   -->: Install was specified. Beginning Install of all Updates
[5] [Feb 14 10:03:14:161]   -->: Installing 7 Updates
[5] [Feb 14 10:03:14:161]   -->:    Security Update for Windows Server 2008 R2 x64 Edition (KB2790113), Eula Accepted: true
[5] [Feb 14 10:03:14:161]   -->:    Security Update for Windows Server 2008 R2 x64 Edition (KB2778344), Eula Accepted: true
[5] [Feb 14 10:03:14:161]   -->:    Security Update for Windows Server 2008 R2 x64 Edition (KB2790655), Eula Accepted: true
[5] [Feb 14 10:03:14:161]   -->:    Security Update for Microsoft .NET Framework 4 on XP, Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 for x64 (KB2789642), Eula Accepted: true
[5] [Feb 14 10:03:14:161]   -->:    Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2789645), Eula Accepted: true
[5] [Feb 14 10:03:14:161]   -->:    Security Update for Windows Server 2008 R2 x64 Edition (KB2799494), Eula Accepted: true
[5] [Feb 14 10:03:14:161]   -->:    Windows Malicious Software Removal Tool x64 - February 2013 (KB890830), Eula Accepted: true
[5] [Feb 14 10:03:14:161]   -->: 7 Updates are ready to be installed!
[5] [Feb 14 10:03:14:161]   -->: Beginning install ...
[5] [Feb 14 10:03:14:161]   -->: Enumerating result for every single update
[5] [Feb 14 10:03:14:161]   -->:  1. Security Update for Windows Server 2008 R2 x64 Edition (KB2790113): Result Code: Succeeded
[5] [Feb 14 10:03:14:161]   -->:  2. Security Update for Windows Server 2008 R2 x64 Edition (KB2778344): Result Code: Succeeded
[5] [Feb 14 10:03:14:161]   -->:  3. Security Update for Windows Server 2008 R2 x64 Edition (KB2790655): Result Code: Succeeded
[5] [Feb 14 10:03:14:161]   -->:  4. Security Update for Microsoft .NET Framework 4 on XP, Server 2003, Vista, Windows 7, Server 2008, Server 2008 R2 for x64 (KB2789642): Result Code: Succeeded
[5] [Feb 14 10:03:14:161]   -->:  5. Security Update for Microsoft .NET Framework 3.5.1 on Windows 7 and Windows Server 2008 R2 SP1 for x64-based Systems (KB2789645): Result Code: Succeeded
[5] [Feb 14 10:03:14:161]   -->:  6. Security Update for Windows Server 2008 R2 x64 Edition (KB2799494): Result Code: Succeeded
[5] [Feb 14 10:03:14:161]   -->:  7. Windows Malicious Software Removal Tool x64 - February 2013 (KB890830): Result Code: Succeeded
[5] [Feb 14 10:03:14:161]   -->: 
[5] [Feb 14 10:03:14:161]   -->: Overall Result Code: Succeeded
[5] [Feb 14 10:03:14:161]   -->: 
[5] [Feb 14 10:03:14:161]   -->: Install finished, reboot required: YES
[5] [Feb 14 10:03:14:161]   ################################################################
[5] [Feb 14 10:03:14:161]   End including LogFile "C:\tmp\wuinstall.log"
[5] [Feb 14 10:03:14:161]   
[5] [Feb 14 10:03:14:161]   If
[5] [Feb 14 10:03:14:161]   $ExitCode$ =  "0"   <<< result false
[5] [Feb 14 10:03:14:161] Then
[5] [Feb 14 10:03:14:161] 
[5] [Feb 14 10:03:14:161] Else
[5] [Feb 14 10:03:14:161]   
[5] [Feb 14 10:03:14:161]   If
[5] [Feb 14 10:03:14:161]     $ExitCode$ =  "2"   <<< result false
[5] [Feb 14 10:03:14:161]   Then
[5] [Feb 14 10:03:14:161]   
[5] [Feb 14 10:03:14:161]   Else
[5] [Feb 14 10:03:14:161]     
[5] [Feb 14 10:03:14:161]     If
[5] [Feb 14 10:03:14:161]       $ExitCode$ =  "10"   <<< result true
[5] [Feb 14 10:03:14:161]     Then
[5] [Feb 14 10:03:14:161]       comment: successful, reboot required
[5] [Feb 14 10:03:14:162]       ExitWindows set to Immediate Reboot
[5] [Feb 14 10:03:14:162]     
[5] [Feb 14 10:03:14:162]     Else
[5] [Feb 14 10:03:14:162]     EndIf
[5] [Feb 14 10:03:14:162]   EndIf
[5] [Feb 14 10:03:14:162] EndIf
[5] [Feb 14 10:03:14:162] Process stopped
[1] [Feb 14 10:03:14:162] ___________________
[1] [Feb 14 10:03:14:162] script finished
[1] [Feb 14 10:03:14:162] 0 errors
[1] [Feb 14 10:03:14:162] 0 warnings
[1] [Feb 14 10:03:14:162] 
[1] [Feb 14 10:03:14:162] installed product: app_check-wsus Version: 1.0-1
[1] [Feb 14 10:03:14:162] 
[6] [Feb 14 10:03:14:162] Delete "c:\opsi.org\tmp\_winstbat_*"
[6] [Feb 14 10:03:14:162]   Search "c:\opsi.org\tmp\"
[6] [Feb 14 10:03:14:162] Registry key [HKLM\SOFTWARE\opsi.org\winst]  opened
[6] [Feb 14 10:03:14:162]                 Variable "RebootRequested"  had value  "0"
[6] [Feb 14 10:03:14:162]                 Info:    "RebootRequested"  changed to "4"
[6] [Feb 14 10:03:14:162]                 Variable "LastLogFilename"  had value  "c:\tmp\opsi-client-agent.log"
[6] [Feb 14 10:03:14:162]                 Info:    "LastLogFilename"  changed to "c:\tmp\instlog.txt"
[6] [Feb 14 10:03:14:162]                 Variable "ContinueLogFile"  is keeping its value "1"
[6] [Feb 14 10:03:14:162]                 Variable "NumberOfErrors"  not found. Code: 2
[6] [Feb 14 10:03:14:163]                 Variable "NumberOfErrors"  set to "0"
[6] [Feb 14 10:03:14:178]                 Key flushed
[6] [Feb 14 10:03:14:178]                 Key closed
[5] [Feb 14 10:03:14:181] -------- submitted part of log file ends here, see the rest of log file on client ----------
[5] [Feb 14 10:03:14:184] read file created
[5] [Feb 14 10:03:14:184] read file opend
[5] [Feb 14 10:03:14:184] start reading read file ...
[5] [Feb 14 10:03:14:187] start sending read file ...
[6] [Feb 14 10:03:15:643] JSON service request https://192.168.3.5:4447/rpc backend_exit
[6] [Feb 14 10:03:15:696] JSON Bench for backend_exit "params":[],"id":1} Start: 10:03:15:643 Time: 00:00:00:053
[1] [Feb 14 10:03:15:700] ============  opsi-winst Version 4.11.3.3 WIN32 is regularly exiting. Time 2013-02-14  10:03:15 .

Opsiclientd.conf kann ich nicht einfügen, das ist zuviel (überschreitet die erlaubte Zeichengrenze)
Benutzeravatar
SisterOfMercy
Beiträge: 1524
Registriert: 22 Jun 2012, 19:18

Re: Folgeaktion bein Once-Script unerwartet

Beitrag von SisterOfMercy »

Send an e-mail to info(at)uib.de with the logfile as attachment and also a link to your post.
Bitte schreiben Sie Deutsch, when I'm responding in the German-speaking part of the forum!
mufungu
Beiträge: 5
Registriert: 13 Feb 2013, 13:39

Re: Folgeaktion bein Once-Script unerwartet

Beitrag von mufungu »

SisterOfMercy hat geschrieben:Send an e-mail to info(at)uib.de with the logfile as attachment and also a link to your post.
Done, thanks.
mufungu
Beiträge: 5
Registriert: 13 Feb 2013, 13:39

Re: Folgeaktion bein Once-Script unerwartet

Beitrag von mufungu »

Hallo,

ich habe das Problem gefunden. Ich habe fälschlicherweise "Exitwindows /immediatelogout" verwendet, das führte zu dem Fehler.
Problem behoben.

Es handelt sich also definitiv um keinen Bug.

Danke & Gruss

Martin
Antworten