Error: Timeout: Waiting for ending of "hwaudit.exe" stopped - waitSecs out 90 sec
and is cancelling before it completes. How can I increase this timeout? thanks! I am brand new to OPSI and have looked at docs and forum, but am still not sure where I need to go to make this adjustment. So far, seems only to happen to hwaudit. thanks!
hwaudit timing out (swaudit is not) windows client
-
- Beiträge: 3
- Registriert: 18 Sep 2016, 21:15
- n.wenselowski
- Ex-uib-Team
- Beiträge: 3194
- Registriert: 04 Apr 2013, 12:15
Re: hwaudit timing out (swaudit is not) windows client
Hi,
in the config-editor you can specify the timeout.
For this you need to select a client, then switch to the product configuration tab and then select the product hwaudit. On the lower right you will find the properties. The setting you are looking for is timeout.
Bye
Niko
in the config-editor you can specify the timeout.
For this you need to select a client, then switch to the product configuration tab and then select the product hwaudit. On the lower right you will find the properties. The setting you are looking for is timeout.
Bye
Niko
Code: Alles auswählen
import OPSI
-
- Beiträge: 3
- Registriert: 18 Sep 2016, 21:15
Re: hwaudit timing out (swaudit is not) windows client
Hi Niko,
I actually just found the same location as I was about to read your response!
I had not looked in the opsi-configed screens, only at the linux level on the opsi-server. I see what you are referring to now. Just out of curiosity, is there a place at the linux-level where these parameters are also found?
Anyways, thanks so much for your reply!
Mark
I actually just found the same location as I was about to read your response!

Anyways, thanks so much for your reply!
Mark
- n.wenselowski
- Ex-uib-Team
- Beiträge: 3194
- Registriert: 04 Apr 2013, 12:15
Re: hwaudit timing out (swaudit is not) windows client
Hi Mark,
Some people access the data in the backends directly but I would advise against this because it happened more than once that changes rendered data in an incosistent state. The API however is stable since many versions and should be used instead.
To see default settings:
To see custom settings of client abc.de.fg:
If he does not has custom settings defaults will be used. First the settings of the depot and if there aren't any settings made specially for the depot the global settings.
General information and some more examples can be found in the manual.
Bye
Niko
You can always use opsi-admin to access the data through the API.jobsoftinc hat geschrieben:Just out of curiosity, is there a place at the linux-level where these parameters are also found?
Some people access the data in the backends directly but I would advise against this because it happened more than once that changes rendered data in an incosistent state. The API however is stable since many versions and should be used instead.
To see default settings:
Code: Alles auswählen
opsi-admin -d method productProperty_getObjects '' '{"productId": "hwaudit"}'
Code: Alles auswählen
opsi-admin -d method productPropertyState_getObjects '' '{"productId": "hwaudit", "objectId": "abc.de.fg"}'
General information and some more examples can be found in the manual.
Bye
Niko
Code: Alles auswählen
import OPSI