Seite 1 von 1
IsSuccess fehlerhaft
Verfasst: 12 Jun 2014, 13:43
von embl-structures
Hallo,
wie in
viewtopic.php?f=5&t=6549 besprochen hier ein Bugreport fuer IsSuccess in W_inst 4.11.3.11. Diese Funktion hat leider schwerwiegende Probleme. Das Skript
Code: Alles auswählen
[Initial]
SetLogLevel = 6
[Aktionen]
IsSuccess
DefVar $test$
Set $test$ = "gut"
if $test$ = "gut"
PAUSE $test$
else
PAUSE "SCHLECHT"
endif
Einmal als localboot und einmal direkt in der WInst-Konsole auf demselben Rechner ausgefuehrt ergibt verschiedene Fehlermeldungen, funktioniert aber in keinem Fall. Das Testsystem ist eine virtuelle Maschine mit Windows 7 Pro 64bit.
Ausfuehrung als localboot Produkt (via "fire on_demand event")
IsSuccess wird im Log mit "Set: Exit Script as successful" quittiert und danach wird direkt bei "if $test$ = "gut"" weitergefahren
Lokale Ausfuehrung in der WInst-Konsole
IsSuccess wird im Log mit "Syntax Error in Section: Actions (Command in line 5): IsSuccess -> undefined" quittiert und die Abarbeitung auch nach Abklicken von "Exit" beim "if $test$ = "gut"" weitergefahren
Die Logfiles sind recht lang, aber leider laesst sich kein Dateianhang hochladen (Fehlermeldung "Das Kontingent für Dateianhänge ist bereits vollständig ausgenutzt"). Koennte man das Kontingent bitte erhoehen damit ich die Logfiles hochladen kann?
Gruss
frank
Re: IsSuccess fehlerhaft
Verfasst: 12 Jun 2014, 13:59
von embl-structures
Zur Weiteren Abarbeitung des Skriptes nach Klicken von "Exit" siehe auch
viewtopic.php?f=7&t=3760&p=28090#p28090
Re: IsSuccess fehlerhaft
Verfasst: 12 Jun 2014, 16:37
von dkoch
embl-structures hat geschrieben:
Die Logfiles sind recht lang, aber leider laesst sich kein Dateianhang hochladen (Fehlermeldung "Das Kontingent für Dateianhänge ist bereits vollständig ausgenutzt"). Koennte man das Kontingent bitte erhoehen damit ich die Logfiles hochladen kann?
Hallo EMBL,
Entweder hier direkt als Text posten oder eine paste service verwenden wie
http://paste.debian.net/
Liebe Grüße,
Daniel
Re: IsSuccess fehlerhaft
Verfasst: 12 Jun 2014, 16:46
von embl-structures
Na dann:
Logfile wenn als localboot Produkt ausgefuehrt
Code: Alles auswählen
[1] [Jun 12 13:26:10:904] opsi-winst 4.11.3.11 started at >>6/12/2014 13:26:09
[1] [Jun 12 13:26:10:904] startmessage opsi-winst created at CentralForm.FormCreate: 6/12/2014 13:26:09
[1] [Jun 12 13:26:10:904] Loading skin from: C:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-winst\winstskin
[1] [Jun 12 13:26:10:904] startmessage StartProgramModes and create log: 6/12/2014 13:26:09
[1] [Jun 12 13:26:10:904] startmessage start opsi service connection: 6/12/2014 13:26:09
[1] [Jun 12 13:26:10:904] JSON Bench for backend_info "params":[],"id":1} Start: 13:26:09:325 Time: 00:00:01:574
[1] [Jun 12 13:26:10:904] startmessage create log: 6/12/2014 13:26:10
[6] [Jun 12 13:26:10:905] JSON service request https://my.opsi.server:4447/rpc getDepotId
[6] [Jun 12 13:26:11:081] JSON Bench for getDepotId "params":["myhost.domain.de"],"id":1} Start: 13:26:10:904 Time: 00:00:00:177
[6] [Jun 12 13:26:11:084] JSON service request https://my.opsi.server:4447/rpc backend_setOptions
[6] [Jun 12 13:26:11:144] JSON Bench for backend_setOptions "params":[{"processProductOnClientSequence":true}] Start: 13:26:11:084 Time: 00:00:00:060
[6] [Jun 12 13:26:11:148] JSON service request https://my.opsi.server:4447/rpc productOnClient_getObjects
[6] [Jun 12 13:26:11:976] JSON Bench for productOnClient_getObjects "params":["",{"clientId":"myhost.domain.de"," Start: 13:26:11:148 Time: 00:00:00:828
[6] [Jun 12 13:26:11:983] JSON service request https://my.opsi.server:4447/rpc backend_setOptions
[6] [Jun 12 13:26:12:045] JSON Bench for backend_setOptions "params":[{"processProductOnClientSequence":false} Start: 13:26:11:983 Time: 00:00:00:062
[5] [Jun 12 13:26:12:047] Computername:myhost.domain.de
[5] [Jun 12 13:26:12:047] Computername according to Environment Variable :VM-DROSERA-04
[5] [Jun 12 13:26:12:047] opsi service URL https://my.opsi.server:4447
[5] [Jun 12 13:26:12:047] Depot path: P:\install
[5] [Jun 12 13:26:12:047]
[5] [Jun 12 13:26:12:054] bootmode BKSTD
[5] [Jun 12 13:26:12:054] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[5] [Jun 12 13:26:12:054] Resolved sequence of products (6/12/2014 13:26:12):
[5] [Jun 12 13:26:12:054] Product 6 embl-test : always
[5] [Jun 12 13:26:12:054] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[6] [Jun 12 13:26:12:324] [embl-test] JSON service request https://my.opsi.server:4447/rpc getProductProperties_hash
[6] [Jun 12 13:26:12:751] [embl-test] JSON Bench for getProductProperties_hash "params":["embl-test","myhost.domain.de"],"id Start: 13:26:12:324 Time: 00:00:00:427
[6] [Jun 12 13:26:12:755] [embl-test] JSON service request https://my.opsi.server:4447/rpc getProduct_hash
[6] [Jun 12 13:26:12:979] [embl-test] JSON Bench for getProduct_hash "params":["embl-test","sauron.embl.de"],"id":1} Start: 13:26:12:755 Time: 00:00:00:224
[6] [Jun 12 13:26:12:983] [embl-test] JSON service request https://my.opsi.server:4447/rpc productOnClient_getObjects
[6] [Jun 12 13:26:13:083] [embl-test] JSON Bench for productOnClient_getObjects "params":["",{"clientId":"myhost.domain.de"," Start: 13:26:12:982 Time: 00:00:00:101
[5] [Jun 12 13:26:13:086] [embl-test] scriptname: "install.ins", special path: "P:\install\embl-test\"
[1] [Jun 12 13:26:13:098] [embl-test]
[1] [Jun 12 13:26:13:098] [embl-test] ============ Version 4.11.3.11 WIN32 script "P:\install\embl-test\install.ins"
[1] [Jun 12 13:26:13:098] [embl-test] start: 2014-06-12 13:26:13
[1] [Jun 12 13:26:13:098] [embl-test] installing product: embl-test_1.0-1
[1] [Jun 12 13:26:13:098] [embl-test] on client named "myhost.domain.de"
[1] [Jun 12 13:26:13:098] [embl-test] loggedin user "admin"
[1] [Jun 12 13:26:13:098] [embl-test] winst running as "SYSTEM"
[1] [Jun 12 13:26:13:098] [embl-test] winst running with admin privileges
[1] [Jun 12 13:26:13:098] [embl-test] winst running in standard script mode
[1] [Jun 12 13:26:13:098] [embl-test] executing: "C:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-winst\winst32.exe"
[1] [Jun 12 13:26:13:098] [embl-test] system infos:
[1] [Jun 12 13:26:13:100] [embl-test] xx-xx-xx-xx-xx-xx - PC hardware address
[1] [Jun 12 13:26:13:100] [embl-test] myhost.domain.de - IP name
[1] [Jun 12 13:26:13:100] [embl-test] xx.xx.xx.xx - IP address
[1] [Jun 12 13:26:13:100] [embl-test] ENU - System default locale
[1] [Jun 12 13:26:13:100] [embl-test] MS Windowds 6.1 64 Bit
[1] [Jun 12 13:26:13:100] [embl-test] opsi service version : 4
[1] [Jun 12 13:26:13:100] [embl-test]
[6] [Jun 12 13:26:13:101] [embl-test] Registry key [HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion] opened
[6] [Jun 12 13:26:13:101] [embl-test] Key closed
[1] [Jun 12 13:26:13:171] [embl-test] LogLevel was 6
[1] [Jun 12 13:26:13:171] [embl-test] LogLevel set to 6
[5] [Jun 12 13:26:13:171] [embl-test] Set: Exit Script as successful
[5] [Jun 12 13:26:13:171] [embl-test]
[5] [Jun 12 13:26:13:171] [embl-test] If
[5] [Jun 12 13:26:13:171] [embl-test] <<< syntax error, no result!! - set to false
[2] [Jun 12 13:26:13:171] [embl-test] Syntax Error in Section: Actions (Command in line 10): $test$ = "gut" -> $test$ = "gut" illegal String expression
[2] [Jun 12 13:26:18:367] [embl-test] Syntax Error in Section: Actions (Command in line 10): $test$ = "gut" -> erroneous characters
[5] [Jun 12 13:26:19:079] [embl-test] Then
[5] [Jun 12 13:26:19:083] [embl-test]
[5] [Jun 12 13:26:19:083] [embl-test] Else
[5] [Jun 12 13:26:19:083] [embl-test] EndIf
[5] [Jun 12 13:26:19:083] [embl-test] Process stopped
[1] [Jun 12 13:26:19:083] [embl-test] ___________________
[1] [Jun 12 13:26:19:083] [embl-test] script finished
[1] [Jun 12 13:26:19:083] [embl-test] 2 errors
[1] [Jun 12 13:26:19:083] [embl-test] 0 warnings
[1] [Jun 12 13:26:19:083] [embl-test]
[1] [Jun 12 13:26:19:083] [embl-test] installed product: embl-test Version: 1.0-1
[1] [Jun 12 13:26:19:083] [embl-test]
[6] [Jun 12 13:26:19:083] [embl-test] Delete "c:\opsi.org\tmp\_winstbat_*"
[6] [Jun 12 13:26:19:083] [embl-test] Search "c:\opsi.org\tmp\"
[6] [Jun 12 13:26:19:084] [embl-test] JSON service request https://my.opsi.server:4447/rpc productOnClient_updateObject
[6] [Jun 12 13:26:19:209] [embl-test] JSON Bench for productOnClient_updateObject "params":[{"clientId":"myhost.domain.de","act Start: 13:26:19:084 Time: 00:00:00:125
[6] [Jun 12 13:26:19:214] Registry key [HKLM\SOFTWARE\opsi.org\winst] opened
[6] [Jun 12 13:26:19:214] Variable "RebootRequested" is keeping its value "0"
[6] [Jun 12 13:26:19:214] Variable "LastLogFilename" is keeping its value "c:\tmp\instlog.txt"
[6] [Jun 12 13:26:19:214] Variable "ContinueLogFile" is keeping its value "0"
[6] [Jun 12 13:26:19:214] Variable "NumberOfErrors" not found. Code: 2
[6] [Jun 12 13:26:19:214] Key flushed
[6] [Jun 12 13:26:19:214] Key closed
[5] [Jun 12 13:26:19:217] -------- submitted part of log file ends here, see the rest of log file on client ----------
[5] [Jun 12 13:26:19:219] read file created
[5] [Jun 12 13:26:19:219] read file opend
[5] [Jun 12 13:26:19:219] start reading read file ...
[5] [Jun 12 13:26:19:220] start sending read file ...
[6] [Jun 12 13:26:19:284] JSON service request https://my.opsi.server:4447/rpc backend_exit
[6] [Jun 12 13:26:19:339] JSON Bench for backend_exit "params":[],"id":1} Start: 13:26:19:284 Time: 00:00:00:055
[1] [Jun 12 13:26:19:341] ============ opsi-winst Version 4.11.3.11 WIN32 is regularly exiting. Time 2014-06-12 13:26:19 .
2 13:10:29 .
Logfile wenn lokal in WInst-Konsole ausgefuehrt
Code: Alles auswählen
[5] [6/12/2014 16:44:05] --
[5] [6/12/2014 16:44:05] --
[1] [6/12/2014 16:44:05] opsi-winst 4.11.3.2 started at 6/12/2014 16:43:49
[1] [6/12/2014 16:44:05]
[1] [6/12/2014 16:44:05] ============ Version 4.11.3.2 WIN32 script "C:\Users\admin\Desktop\exittest.ins"
[1] [6/12/2014 16:44:05] start: 2014-06-12 16:44:05
[1] [6/12/2014 16:44:05] on client named "MYHOST"
[1] [6/12/2014 16:44:05] loggedin user "admin"
[1] [6/12/2014 16:44:05] winst running as "admin"
[1] [6/12/2014 16:44:05] winst running with admin privileges
[1] [6/12/2014 16:44:05] winst running in standard script mode
[1] [6/12/2014 16:44:05] [executing: "C:\tmp\opsi\opsi-winst\winst32.exe"]
[1] [6/12/2014 16:44:05] system infos:
[1] [6/12/2014 16:44:05] xx-xx-xx-xx-xx-xx - PC hardware address
[1] [6/12/2014 16:44:05] myhost.embl.de - IP name
[1] [6/12/2014 16:44:05] xx.xx.xx.xx - IP address
[1] [6/12/2014 16:44:05] ENU - System default locale
[1] [6/12/2014 16:44:05] MS Windowds 6.1 64 Bit
[1] [6/12/2014 16:44:05]
[6] [6/12/2014 16:44:05] Registry key [HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion] opened
[6] [6/12/2014 16:44:05] Key closed
[1] [6/12/2014 16:44:05] LogLevel was 6
[1] [6/12/2014 16:44:05] LogLevel set to 6
[2] [6/12/2014 16:44:05] Syntax Error in Section: Actions (Command in line 5): IsSuccess -> undefined
[5] [6/12/2014 16:44:08]
[5] [6/12/2014 16:44:08] If
[5] [6/12/2014 16:44:08] <<< syntax error, no result!! - set to false
[2] [6/12/2014 16:44:08] Syntax Error in Section: Actions (Command in line 10): $test$ = "gut" -> $test$ = "gut" illegal String expression
[2] [6/12/2014 16:44:09] Syntax Error in Section: Actions (Command in line 10): $test$ = "gut" -> erroneous characters
[5] [6/12/2014 16:44:09] Then
[5] [6/12/2014 16:44:09]
[5] [6/12/2014 16:44:09] Else
[5] [6/12/2014 16:44:09] EndIf
[5] [6/12/2014 16:44:09] Process stopped
[1] [6/12/2014 16:44:09] ___________________
[1] [6/12/2014 16:44:09] script finished
[1] [6/12/2014 16:44:09] 3 errors
[1] [6/12/2014 16:44:09] 0 warnings
[1] [6/12/2014 16:44:09]
[1] [6/12/2014 16:44:09]
[6] [6/12/2014 16:44:09] Delete "c:\opsi.org\tmp\_winstbat_*"
[6] [6/12/2014 16:44:09] Search "c:\opsi.org\tmp\"
Gruss
frank
Re: IsSuccess fehlerhaft
Verfasst: 12 Jun 2014, 18:27
von dkoch
embl-structures hat geschrieben:Na dann:
Logfile wenn als localboot Produkt ausgefuehrt
Code: Alles auswählen
[1] [Jun 12 13:26:10:904] opsi-winst 4.11.3.11 started at >>6/12/2014 13:26:09
Logfile wenn lokal in WInst-Konsole ausgefuehrt
Code: Alles auswählen
[1] [6/12/2014 16:44:05] opsi-winst 4.11.3.2 started at 6/12/2014 16:43:49
Das erklärt wahrscheinlich wieso die Winst-Konsole
liefert. Warum nach IsSuccess weiter evaluiert wird allerdings nicht
Edit:
opsi-winst (4.11.3.7) stable; urgency=low
* changed DsiWin32 to work with lazarus 1.0.8/fpc 2.6.2
* new command: isSuccess : Terminates Script execution with out error
* new command: noUpdateScript : Do not run a update after setup script even if it is there and we are not failed
* new function emptylist
* new function getlistcontainingList
-- Detlef Oertel <
d.oertel@uib.de> Tue, 29 Jul 2013:15:00:00 +0200
Die Funktion kam in 4.11.3.7 hinzu. Damit wäre das Problem bei der Konsole geklärt
Re: IsSuccess fehlerhaft
Verfasst: 12 Jun 2014, 18:32
von embl-structures
dkoch hat geschrieben:
Logfile wenn lokal in WInst-Konsole ausgefuehrt
Code: Alles auswählen
[5] [6/12/2014 16:44:05] --
[5] [6/12/2014 16:44:05] --
[1] [6/12/2014 16:44:05] opsi-winst 4.11.3.2 started at 6/12/2014 16:43:49
Das erklärt wahrscheinlich wieso die Winst-Konsole ...
Hmm. Woher soll ich die Konsole denn nehmen? Ich verwende im Moment C:\tmp\opsi\opsi-winst\winst32.exe.
frank
Re: IsSuccess fehlerhaft
Verfasst: 13 Jun 2014, 09:35
von n.wenselowski
Hallo Frank,
embl-structures hat geschrieben:Hmm. Woher soll ich die Konsole denn nehmen? Ich verwende im Moment C:\tmp\opsi\opsi-winst\winst32.exe.
Ich verwende meist den aus
C:\Programme (x86)\opsi.org/opsi-client-agent\opsi-winst
Gruß
Niko
Re: IsSuccess fehlerhaft
Verfasst: 13 Jun 2014, 09:40
von embl-structures
n.wenselowski hat geschrieben:[...]
Ich verwende meist den aus C:\Programme (x86)\opsi.org/opsi-client-agent\opsi-winst
Habe ich auch probiert, aber da erhalte ich die Fehlermeldung
Windows hat geschrieben:
C:\Program Files (x86)\opsi.org\opsi-client-agent\opsi-winst\winst32.exe
[Content]
Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.
Ich versuche es als Administrator und es funktioniert auch nicht mit "Run as Administrator". Habe OPSI auf dieser Maschine gestern komplett neu installiert. ...??
frank
Re: IsSuccess fehlerhaft
Verfasst: 23 Jun 2014, 08:59
von r.witzel
Das Ding gehört System - du musst dir die Rechte besorgen indem du (aber nur auf einem Testgerät) den kompletten OPSI-Ordner unterhalb Programme redundant dem Admin zu eigen machst.