Seite 1 von 1

Opsi timeout error : timed out after 15seconds (errno 103)

Verfasst: 14 Apr 2012, 01:20
von Othmane
I can not activated hwaudit / swaudit, or even reboot my client since OPSI-CONFIGED!

I receive this message: windows-6f5ad89.opsidemo.est-umi.ac.ma OPSI timeout error: After 15seconds timed out (errno 103) Caused connection abort Software)

Re: Opsi timeout error : timed out after 15seconds (errno 10

Verfasst: 14 Apr 2012, 18:03
von d.oertel
Hi,

sorry - but it seems that you did not read and used the getting started manual step by step.
You should do this in order to get all things working.

The error message you describes will be apear if there is no opsi-client-agent on the client.
have al look over here:
http://download.uib.de/opsi_stable/doc/ ... ntegration

or see here
http://opsi-fr.opensides.be/opsi-doc/st ... arted.html

cheers
d.oertel

Re: Opsi timeout error : timed out after 15seconds (errno 10

Verfasst: 14 Apr 2012, 19:05
von Othmane
sorry but I have followed the step "Usage of service_setup.cmd" and I mount the share and I executed "sercive_setup.cmd". So I have installed OPSI-CLIENT-AGENT on my client machine, in a same time I saw the name of my client machine is added to the list of clients on my OPSI-CONFIGED! please help me

Re: Opsi timeout error : timed out after 15seconds (errno 10

Verfasst: 16 Apr 2012, 14:01
von d.oertel
Hi,

ok - sounds good.
I will try to help you.
Please go to your opsi-configed, select the client, than switch to the product tab and set the action request for swaudit to setup.
Now reboot your client.
The product swaudit should be executed after reboot.
If not - post your c:\tmp\opsiclientd.log

regards

d.oertel

Re: Opsi timeout error : timed out after 15seconds (errno 10

Verfasst: 18 Apr 2012, 02:46
von Othmane
that my folder tmp & opsi-client-agent.log : http://www.sendspace.com/file/6rr11g

thank you .

Re: Opsi timeout error : timed out after 15seconds (errno 10

Verfasst: 18 Apr 2012, 10:29
von ueluekmen
Please post the Versions of opsi-packages you use.

In the Archive from the logfiles is no opsiclientd.log. When these log-File is not generated, the opsiclientd is not started, or not working, please check first in your services the status from opsiclientd service.