unable to deploy products from server to client

[Zer0dat1]

Hi ,

I'm new to Opsi, I just completed my opsi server setup and now trying to setup/deploy products using "requested action :setup" under Product configuration tab, but unfortunately I'm receiving below error. My client machine is running windows server 2012R2 and currently on the same IP range as my opsi server (RHEL7.2), opsi-agent-client has been installed on client machine successfully and currently running. Thanks for your support.


error:

Opsi timeout error: Timed out after 15 seconds (last error: [Errno 103] Software caused connection abort

[uncle_scrooge]

Your client's current IP address matches the one shown in ConfigEd under 'Clients' tab?
Your client's firewall is down? Or configured to accept connections to port 4441 from your OPSI server?

[m.radtke]

Hi
Most important:
does your client have the opsi-client-agent installed?

Cheers
Mathias

[Zer0dat1]

Hi uncle_scrooge and mathias,

Please see my response below, thank you in advance.

1. Your client's current IP address matches the one shown in ConfigEd under 'Clients' tab? -> yes, i added the client manually and configured the IP address entry.

2. Your client's firewall is down? Or configured to accept connections to port 4441 from your OPSI server? -> firewall on opsi server and client are both disabled. If i have missed on the manual, do i need to configure port 4441 and 4447 manually on client? Did a telnet test on the client itself using its own IP, I'm not able to telnet to service port 4441 and 4447.

3. does your client have the opsi-client-agent installed? -> yes, i was able to install it by mounting \\<opsiserver>\opsi_depot to client and run service_setup.cmd, the setup completed successfully, I can see opsiconfd services running on the client as well.

[uncle_scrooge]

- Your client has been restarted after installing OPSI client?

- Run a netstat -ab on your client.
There should be something like that:
TCP 0.0.0.0:4441 <YOURMACHINENAME>:0 LISTENING
[opsiclientd.exe]

- In c:\opsi.org\log there is a log opsiclientd.log. Check for obvious errors.
Or provide the content. PasteBin or similar would be an idea.

Thanks.

[goudeuk]

I'm new to OPSI too but maybe you could give opsiconfd service a restart?

Also you could test accessing the opsi management interface (configed) from the client.

[Zer0dat1]

Hi,

Client was already rebooted several times prior to troubleshooting, I have rebooted again and captured opsiclientd.log and opsi_loginblocker.log.

Refer to netstat -ab output ,I can only see below ports currently being used by opsiclient.exe. There are no process listening to ports 4441 and 4447.

TCP 127.0.0.1:49181 SGUATWINCLNT01:49182 ESTABLISHED
[opsiclientd.exe]
TCP 127.0.0.1:49182 SGUATWINCLNT01:49181 ESTABLISHED
[opsiclientd.exe]

########################## opsiclientd.log ################################################################################

[6] [Apr 11 20:58:33] [ opsiclientd ] Setting config value global.log_file (Config.pyo|203)
[6] [Apr 11 20:58:33] [ opsiclientd ] Setting config value global.log_level (Config.pyo|203)
[6] [Apr 11 20:58:33] [ opsiclientd ] Setting config value global.host_id (Config.pyo|203)
[3] [Apr 11 20:58:33] [ opsiclientd ] Failed to read config file 'C:\Program Files (x86)\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf': Bad object id: 'sguatwinclnt01.<dnsdomain>' (Config.pyo|327)
[2] [Apr 11 20:58:33] [ opsiclientd ] Traceback: (Logger.pyo|753)
[2] [Apr 11 20:58:33] [ opsiclientd ] File "ocdlib\Config.pyo", line 323, in readConfigFile
(Logger.pyo|753)
[2] [Apr 11 20:58:33] [ opsiclientd ] File "ocdlib\Config.pyo", line 216, in set
(Logger.pyo|753)
[2] [Apr 11 20:58:33] [ opsiclientd ] File "OPSI\Types.pyo", line 277, in forceFqdn
(Logger.pyo|753)
[2] [Apr 11 20:58:33] [ opsiclientd ] File "OPSI\Types.pyo", line 577, in forceObjectId
(Logger.pyo|753)
[2] [Apr 11 20:58:33] [ opsiclientd ] ==>>> Bad object id: 'sguatwinclnt01.<dnsdomain>' (Config.pyo|328)
[5] [Apr 11 20:58:33] [ opsiclientd ] Setting locale dir to 'C:\Program Files (x86)\opsi.org\opsi-client-agent\locale' (Localization.pyo|59)
[5] [Apr 11 20:58:33] [ opsiclientd ] Loading translation for language 'en' (Localization.pyo|61)
[3] [Apr 11 20:58:33] [ opsiclientd ] Locale not found: [Errno 2] No translation file found for domain: 'opsiclientd' (Localization.pyo|64)
[1] [Apr 11 20:58:33] [ opsiclientd ] Opsiclientd version: 4.0.90 (full) (Opsiclientd.pyo|234)
[1] [Apr 11 20:58:33] [ opsiclientd ] Commandline: C:\Program Files (x86)\opsi.org\opsi-client-agent\opsiclientd.exe (Opsiclientd.pyo|239)
[1] [Apr 11 20:58:33] [ opsiclientd ] Working directory: C:\Windows\system32 (Opsiclientd.pyo|241)
[5] [Apr 11 20:58:33] [ opsiclientd ] Using host id 'sguatwinclnt01.msbu.nec.com.sg' (Opsiclientd.pyo|243)
[5] [Apr 11 20:58:33] [ opsiclientd ] Block login now set to 'True' (Opsiclientd.pyo|109)
[5] [Apr 11 20:58:33] [ opsiclientd ] Starting reactor (Opsiclientd.pyo|249)
[5] [Apr 11 20:58:34] [ opsiclientd ] Starting control pipe (Opsiclientd.pyo|262)
[6] [Apr 11 20:58:34] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Apr 11 20:58:34] [ opsiclientd ] Control pipe started (Opsiclientd.pyo|266)
[5] [Apr 11 20:58:34] [ opsiclientd ] Starting control server (Opsiclientd.pyo|271)
[6] [Apr 11 20:58:34] [ control server ] ControlServer initiated (ControlServer.pyo|390)
[5] [Apr 11 20:58:34] [ opsiclientd ] Control server started (Opsiclientd.pyo|280)
[6] [Apr 11 20:58:34] [ control server ] creating root resource (ControlServer.pyo|397)
[5] [Apr 11 20:58:34] [ opsiclientd ] Starting cache service (Opsiclientd.pyo|288)
[3] [Apr 11 20:58:34] [ control server ] Cannot add static content '/': directory 'static_html' does not exist. (ControlServer.pyo|424)
[5] [Apr 11 20:58:34] [ opsiclientd ] Cache service started (Opsiclientd.pyo|292)
[2] [Apr 11 20:58:34] [ control server ] Traceback: (Logger.pyo|753)
[6] [Apr 11 20:58:34] [ event generator panic ] Initializing event generator '<PanicEventGenerator panic>' (Events.pyo|475)
[5] [Apr 11 20:58:34] [ opsiclientd ] Event generator '<PanicEventGenerator panic>' started (Opsiclientd.pyo|305)
[2] [Apr 11 20:58:34] [ control server ] File "ocdlib\ControlServer.pyo", line 403, in run
(Logger.pyo|753)
[6] [Apr 11 20:58:34] [ event generator panic ] Activating event generator '<PanicEventGenerator panic>' (Events.pyo|483)
[2] [Apr 11 20:58:34] [ control server ] File "twisted\internet\posixbase.pyo", line 504, in listenSSL
(Logger.pyo|753)
[5] [Apr 11 20:58:34] [ opsiclientd ] No events processing, unblocking login (Opsiclientd.pyo|320)
[6] [Apr 11 20:58:34] [ event generator panic ] Getting next event... (Events.pyo|485)
[2] [Apr 11 20:58:34] [ control server ] File "twisted\protocols\tls.pyo", line 865, in __init__
(Logger.pyo|753)
[5] [Apr 11 20:58:34] [ opsiclientd ] Block login now set to 'False' (Opsiclientd.pyo|109)
[2] [Apr 11 20:58:34] [ control server ] File "twisted\protocols\tls.pyo", line 743, in __init__
(Logger.pyo|753)
[2] [Apr 11 20:58:34] [ control server ] File "OPSI\Service\__init__.pyo", line 47, in getContext
(Logger.pyo|753)
[2] [Apr 11 20:58:34] [ control server ] ==>>> Server key file u'opsiclientd.pem' does not exist! (ControlServer.pyo|409)
[5] [Apr 11 20:58:34] [ control server ] Control server exiting (ControlServer.pyo|410)
[6] [Apr 11 20:59:38] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Apr 11 20:59:38] [ control pipe ] -----> Executing: isRebootRequested() (JsonRpc.pyo|134)
[6] [Apr 11 20:59:38] [ control pipe ] Got result (JsonRpc.pyo|142)
[6] [Apr 11 20:59:38] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Apr 11 20:59:38] [ control pipe ] -----> Executing: isShutdownRequested() (JsonRpc.pyo|134)
[6] [Apr 11 20:59:38] [ control pipe ] Got result (JsonRpc.pyo|142)
[6] [Apr 11 20:59:38] [ control pipe ] Creating pipe \\.\pipe\opsiclientd (ControlPipe.pyo|253)
[5] [Apr 11 20:59:38] [ control pipe ] -----> Executing: getBlockLogin() (JsonRpc.pyo|134)
[5] [Apr 11 20:59:38] [ opsiclientd ] rpc getBlockLogin: blockLogin is 'False' (ControlPipe.pyo|428)
[6] [Apr 11 20:59:38] [ control pipe ] Got result (JsonRpc.pyo|142)

################# opsi_loginblocker.log ##################################################
----------------
[5] 2017-04-11 20:52:18 START OpsiLoginBlocker
[5] 2017-04-11 20:52:18 ------------------------------------------------------------------------------------
[5] 2017-04-11 20:52:18 Getting config from registry
[5] 2017-04-11 20:52:18 LoginBlockerLogLevel is: 5
[5] 2017-04-11 20:52:18 Read LoginBlockerLogDir from Registry and switch to Logfile 'c:\opsi.org\log'
[5] 2017-04-11 20:52:18 According to LoginBlockerLogDir Logfile='c:\opsi.org\log\opsi_loginblocker.log'
[5] 2017-04-11 20:52:18 LoginBlockerStart is: 1
[5] 2017-04-11 20:52:18 LoginBlockerTimeoutConnect is: 120 seconds
[5] 2017-04-11 20:52:18 Config read from registry.
[5] 2017-04-11 20:52:18 handleLogfileAging started.
[5] 2017-04-11 20:52:18 Check logfile age: 11.4.2017 - current date: 11.4.2017
[5] 2017-04-11 20:52:18 ------------------------------------------------------------------------
[5] 2017-04-11 20:52:18 Keep current logfile.
[5] 2017-04-11 20:52:18 ------------------------------------------------------------------------
[5] 2017-04-11 20:52:18 OS Version: 6.3 (Windows 8.1)
[5] 2017-04-11 20:52:18 Filtering credential providers
[5] 2017-04-11 20:52:18 Registry: start of opsiclientd service is enabled, waiting for service to start ...
[5] 2017-04-11 20:52:18 Service opsiclientd is running (SERVICE_RUNNING).
[5] 2017-04-11 20:52:18 no Reboot requested.
[5] 2017-04-11 20:52:18 no Shutdown requested.
[5] 2017-04-11 20:52:18 Stop blocking!
[5] 2017-04-11 20:59:38 ------------------------------------------------------------------------------------
[5] 2017-04-11 20:59:38 START OpsiLoginBlocker
[5] 2017-04-11 20:59:38 ------------------------------------------------------------------------------------
[5] 2017-04-11 20:59:38 Getting config from registry
[5] 2017-04-11 20:59:38 LoginBlockerLogLevel is: 5
[5] 2017-04-11 20:59:38 Read LoginBlockerLogDir from Registry and switch to Logfile 'c:\opsi.org\log'
[5] 2017-04-11 20:59:38 According to LoginBlockerLogDir Logfile='c:\opsi.org\log\opsi_loginblocker.log'
[5] 2017-04-11 20:59:38 LoginBlockerStart is: 1
[5] 2017-04-11 20:59:38 LoginBlockerTimeoutConnect is: 120 seconds
[5] 2017-04-11 20:59:38 Config read from registry.
[5] 2017-04-11 20:59:38 handleLogfileAging started.
[5] 2017-04-11 20:59:38 Check logfile age: 11.4.2017 - current date: 11.4.2017
[5] 2017-04-11 20:59:38 ------------------------------------------------------------------------
[5] 2017-04-11 20:59:38 Keep current logfile.
[5] 2017-04-11 20:59:38 ------------------------------------------------------------------------
[5] 2017-04-11 20:59:38 OS Version: 6.3 (Windows 8.1)
[5] 2017-04-11 20:59:38 Filtering credential providers
[5] 2017-04-11 20:59:38 Registry: start of opsiclientd service is enabled, waiting for service to start ...
[5] 2017-04-11 20:59:38 Service opsiclientd is running (SERVICE_RUNNING).
[5] 2017-04-11 20:59:38 no Reboot requested.
[5] 2017-04-11 20:59:38 no Shutdown requested.
[5] 2017-04-11 20:59:38 Stop blocking!

[uncle_scrooge]

Well... Err... Yes... No...
If your client isn't listening on port 4441 there's something terrible broken, I'd say.
Any policies in place that may prevent using this port?

One might try to narrow down the problem with the OPSI client.
But I would go this way: uninstall it - clean up all remnants of OPSI - install the client again.
If the problem still persists we'll have to dive deeper.

Thanks.

Edith says:
As you are evaluating OPSI, I'd like to say that it isn't usual that the client install fails or gets broken.
Maybe cosmic radiation. (As an IBM technician tried to explain our SAN-Problems once.)

[ngbr]

Hi Zer0dat1,

please make sure you always use FQDN for Clients and Server . Your logg says (line 3)

[3] [Apr 11 20:58:33] [ opsiclientd ] Failed to read config file 'C:\Program Files (x86)\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf': Bad object id: 'sguatwinclnt01.<dnsdomain>' (Config.pyo|327)

which way did you go to deploy your agent ?
if you mounted the opsi_depot - share and ran the service_setup.cmd script, most likely your client computer has to be renamed to machine.fq.dn .
if you used the opsi-deploy-client-agent in the script, please provide an fqdn (now I believe this script will fail if no fqdn is provided.

best is to delete the client via the GUI, and re-install the agent. no uninstall needed before, I think ..

[Zer0dat1]

@uncle_scrooge,

Got a spare test client and did the same opsi-client-agent installation by mounting the depot and running setup script, able to successfully install it. But notice that it still does not listen to port 4441 (using netstat -ab). I guess this could be the main issue as my opsi server is not able to communicate to my client via port 4441 , though my clients are able to telnet opsi server via 4777. Just to add some info, my opsi server is not connected to domain, while my clients are connected. Though the host file of my opsi server is updated with the clients IP, FQDN, and hostname. My client machines are currently hardened, but I don't think there will be restrictions in configuring service ports (will need to search on this).

@ngbr,

I removed the client from GUI and registered a new one using the FQDN (initially i'm using hostname only). Still facing the same error. Just want to clarify, will I have issue knowing my server is not connected to domain , while my clients are connected? Or as long they can communicate to each other via service ports (4441, 4447) I'm good to go?