Problem nach Update

[lordbernd]

Hi OPSI Freunde

Hab letzte Woche ein Update von Debian 5.0 auf 6.0 durchgeführt. Dort ist auch gleich das Update für den OPSI mitgekommen und hat sich stressfrei installiert. Beim deployen von einem neuen Rechner ist mir jedoch aufgefallen, dass ich diesen nicht mehr wie gewohnt über den FQDN oder Hostnamen deployen kann, da immer der Fehler mit " Out Of MEMORY" auftritt. Nach längeren Versuchen den Rechner zu deployen, habe ich es über die IP geschafft und gehofft, ihr fixt den Bug mit dem nächsten Update.

Letzte Woche war es dann soweit. Ich sollte einen stink normalen Rechner deployen und Softwaretechnisch soweit herrichten, dass damit gearbeitet werden kann. Hab dann gleich losgelegt und es haben sich auch sofort die ersten Probleme dargestellt. Der Rechner lies sich zwar ganz normal über die shell deployen, jedoch konnte ich keine Software über das Webinterface installieren. Wenn man auf "on Demand" klickt, wird zwar der OPSI Agent remote gestartet, jedoch bricht dieser mit einer langen Fehlermeldung, die ich nicht lesen kann, ab. Durchsuchen der OPSI-Client-agent Logs brachte mich auch nicht weiter, da dort nichts von diesem Problem zu finden war. Nach mehreren versuchen konnte ich dann aus der Fehlermeldung sowas ählnliches wie "Authentification failed!" herrauslesen. Hab dann versucht den Lokalen User zu resetten, alle User auf dem Opsi überprüft, ob sie nicht abgelaufen sind, die Gruppen gecheckt, OPSI mit dem Rechtecheck neu gestartet, Maschiene rebootet.... alles ohne Erfolg. Im Log steht wie gesagt nichts über "Auth. failed", jedoch findet man ab 2/3 die Meldung:

Code: Alles auswählen

[5] [02.05.2011 12:04:41] 
[5] [02.05.2011 12:04:41] If
[5] [02.05.2011 12:04:41]     "c:\tmp\opsi": File Error 2 (Das System kann die angegebene Datei nicht finden)
[5] [02.05.2011 12:04:41]   fileExists("c:\tmp\opsi")   <<< result false
[5] [02.05.2011 12:04:41] Then
[5] [02.05.2011 12:04:41] EndIf
[5] [02.05.2011 12:04:41] 
[5] [02.05.2011 12:04:41] If
[5] [02.05.2011 12:04:41]     "c:\tmp\opsi-client-agent": File Error 2 (Das System kann die angegebene Datei nicht finden)
[5] [02.05.2011 12:04:41]   fileExists("c:\tmp\opsi-client-agent")   <<< result false
[5] [02.05.2011 12:04:41] Then
[5] [02.05.2011 12:04:41] EndIf
[5] [02.05.2011 12:04:41] 
[5] [02.05.2011 12:04:41] If
[5] [02.05.2011 12:04:41]     "c:\tmp\python": File Error 2 (Das System kann die angegebene Datei nicht finden)
[5] [02.05.2011 12:04:41]   fileExists("c:\tmp\python")   <<< result false
[5] [02.05.2011 12:04:41] Then
[5] [02.05.2011 12:04:41] EndIf
[5] [02.05.2011 12:04:41] 
[5] [02.05.2011 12:04:41] Execution of Files_del_utils
[4] [02.05.2011 12:04:41]   Warning: Directory C:\Program Files (x86)\opsi.org\opsi-client-agent\utils\ does not exist, nothing deleted
[5] [02.05.2011 12:04:41] 
[5] [02.05.2011 12:04:41] If
[5] [02.05.2011 12:04:41]     "C:\Program Files (x86)\opsi.org\preloginloader\": File Error 2 (Das System kann die angegebene Datei nicht finden)
[5] [02.05.2011 12:04:41]   FileExists("C:\Program Files (x86)\opsi.org\preloginloader\")   <<< result false
[5] [02.05.2011 12:04:41] Then
[5] [02.05.2011 12:04:41] EndIf
[5] [02.05.2011 12:04:41] comment: all is done but make a reboot after terminating with the script
[5] [02.05.2011 12:04:41] 
[5] [02.05.2011 12:04:41] If
[5] [02.05.2011 12:04:41]   $INST_AllowReboot$ = "true"   <<< result false
[5] [02.05.2011 12:04:41]   ($INST_AllowReboot$ = "true")   <<< result false
[5] [02.05.2011 12:04:41] Then
[5] [02.05.2011 12:04:41] EndIf
[1] [02.05.2011 12:04:41] ___________________
[1] [02.05.2011 12:04:41] script finished
[1] [02.05.2011 12:04:41] 12 errors
[1] [02.05.2011 12:04:41] 2 warnings
[1] [02.05.2011 12:04:41] 
[1] [02.05.2011 12:04:41] 
[1] [02.05.2011 12:04:41] ============  winst Version 4.10.8.7 WIN32 is regularly exiting. Time 2011-05-02  12:04:41 .

welche ich nicht nachvollziehen kann In der Config.ini vom Opsi-client-Agent steht nichts von diesem "Speziellen" Programm-Pfad. Der Rechner lauft auf Windows 7 Pro x64. Ich hab mit dem OPSI schon mindestens 10 baugleiche Rechner deployed und installiert, immer Erfolgreich. Hab mir gedacht, ich wart mal, wahrscheinlich kommt eh nächte Woche ein fix raus.

Heute nach der erneuten Fehlersucherei hab ich gesehen, es gibt wieder ein Update. Nun hab ich dieses mit

Code: Alles auswählen

opsi-product-updater -i -vv

gezogen und installiert, da ist jedoch etwas schief gelaufen (Package.log):

Code: Alles auswählen

May 02 10:05:54 [notice] Installing package file '/var/lib/opsi/repository/opsi-client-agent_4.0.1-6.opsi' on depot 'iti10.runningball.local' (Depotserver.py|131)
May 02 10:05:54 [notice] Getting meta data from package '/var/lib/opsi/repository/opsi-client-agent_4.0.1-6.opsi' (Product.py|190)
May 02 10:05:54 [notice] Creating product in backend (Depotserver.py|166)
May 02 10:05:54 [notice] Locking product 'opsi-client-agent' on depot 'iti10.runningball.local' (Depotserver.py|169)
May 02 10:05:54 [notice] Checking package dependencies (Depotserver.py|187)
May 02 10:05:54 [notice] Running preinst script (Depotserver.py|190)
May 02 10:05:54 [notice] Running package script 'preinst' (Product.py|385)
May 02 10:05:55 [notice] Unpacking package files (Depotserver.py|194)
May 02 10:05:55 [notice] Extracting data from package '/var/lib/opsi/repository/opsi-client-agent_4.0.1-6.opsi' (Product.py|236)
May 02 10:05:55 [critical] Traceback: (Logger.py|721)
May 02 10:05:55 [critical]      line 201 in 'installPackage' in file '/usr/lib/pymodules/python2.6/OPSI/Backend/Depotserver.py' (Logger.py|721)
May 02 10:05:55 [critical]      line 300 in 'extractData' in file '/usr/lib/pymodules/python2.6/OPSI/Util/Product.py' (Logger.py|721)
May 02 10:05:55 [critical]      ==>>> Failed to extract data from package '/var/lib/opsi/repository/opsi-client-agent_4.0.1-6.opsi': Failed to extract archive '/var/lib/opsi/repository/opsi-client-agent_4.0.1-6.opsi': [Errno 2] No such file or directory (Depotserver.py|367)

hab es dann erneut veruscht und erhalte im opsi-product-updater.log sowie auch beim Absetzen des Befehls

Code: Alles auswählen

opsi-product-updater -i -vv

folgendes:

Code: Alles auswählen

May 02 10:42:32 [notice] Getting installed products (opsi-product-updater|818)
May 02 10:42:32 [notice] Getting info for local packages in '/var/lib/opsi/repository' (opsi-product-updater|795)
May 02 10:42:33 [notice] Getting package infos from repository 'http://download.uib.de' (opsi-product-updater|834)
May 02 10:42:39 [notice] hwaudit_4.0.2-1.opsi - installation not required: installed version '4.0.2-1' of product 'hwaudit' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] javavm_1.6.0.20-2.opsi - installation not required: installed version '1.6.0.20-2' of product 'javavm' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] jedit_4.3.2-4.opsi - installation not required: installed version '4.3.2-4' of product 'jedit' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] opsi-adminutils_4.0.1.2-1.opsi - installation not required: installed version '4.0.1.2-1' of product 'opsi-adminutils' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] opsi-client-agent_4.0.1-6.opsi - installation not required: installed version '4.0.1-6' of product 'opsi-client-agent' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] opsi-template-with-admin_1.0-5.opsi - installation not required: installed version '1.0-5' of product 'opsi-template-with-admin' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] opsi-template_1.0-20.opsi - installation not required: installed version '1.0-20' of product 'opsi-template' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] opsi-winst_4.10.8.14-1.opsi - installation not required: installed version '4.10.8.14-1' of product 'opsi-winst' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] shutdownwanted_1.0-2.opsi - installation not required: installed version '1.0-2' of product 'shutdownwanted' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] swaudit_4.0-6.opsi - installation not required: installed version '4.0-6' of product 'swaudit' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] xpconfig_2.6-1.opsi - installation not required: installed version '2.6-1' of product 'xpconfig' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] hwinvent_4.0-1.opsi - installation not required: installed version '4.0-1' of product 'hwinvent' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] memtest86_3.5b-1.opsi - installation not required: installed version '3.5b-1' of product 'memtest86' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] ntfs-restore-image_1.5-1.opsi - installation not required: installed version '1.5-1' of product 'ntfs-restore-image' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] ntfs-write-image_1.5-1.opsi - installation not required: installed version '1.5-1' of product 'ntfs-write-image' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] win2k_4.0-4.opsi - installation not required: installed version '4.0-4' of product 'win2k' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] win7-x64_4.0-5.opsi - installation not required: installed version '4.0-5' of product 'win7-x64' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] win7_4.0-5.opsi - installation not required: installed version '4.0-5' of product 'win7' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] win2003-r2-x64_4.0-4.opsi - installation not required: installed version '4.0-4' of product 'win2003-r2-x64' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] win2003_4.0-4.opsi - installation not required: installed version '4.0-4' of product 'win2003' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] win2008-r2_4.0-5.opsi - installation not required: installed version '4.0-5' of product 'win2008-r2' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] win2008-x64_4.0-5.opsi - installation not required: installed version '4.0-5' of product 'win2008-x64' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] win2008_4.0-5.opsi - installation not required: installed version '4.0-5' of product 'win2008' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] winvista-x64_4.0-5.opsi - installation not required: installed version '4.0-5' of product 'winvista-x64' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] winvista_4.0-5.opsi - installation not required: installed version '4.0-5' of product 'winvista' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] winxppro-x64_4.0-4.opsi - installation not required: installed version '4.0-4' of product 'winxppro-x64' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] winxppro_4.0-4.opsi - installation not required: installed version '4.0-4' of product 'winxppro' is up to date (opsi-product-updater|399)
May 02 10:42:39 [notice] wipedisk_1.0-2.opsi - installation not required: installed version '1.0-2' of product 'wipedisk' is up to date (opsi-product-updater|399)

Dann hab ich mir gedacht, wenn ich die verschiedenen opsi-client-agent_4.0.1-6.opsi Files lösche und dann nochmal

Code: Alles auswählen

opsi-product-updater -i -vv

ausführe, sollte er erkennen das da was faul ist. Hab jedoch falsch gedacht

Jetzt stehe ich vor dem Problem, dass der Folder in dem sich der OPSI-Client-Agent befinden sollte nicht mehr existiert und das alte Verzeichniss "opsi-client-agent.tmp" heisst. Wenn ich es versuche per hand zu installieren kommt nur:

Code: Alles auswählen

 
opsi-package-manager opsi-client-agent_4.0.1-6.opsi
ERROR: No command specified

Ansonsten ist OPSI der Meinung alles sei in Ordnung und es ist alles installiert.

Ich hoffe Ihr könnt mir folgen und mit mir gemeinsam das Problem lösen. Falls irgendwas unklar ist oder welche Logs benötigt werden, werde ich euch damit versorgen

Ich geh jetzt mal nach Haus, für heut schon genug geärgert...

LG,
Bernd

[othiman]

Hallo Bernd,

kurzer Hinweis: im Befehl zum manuellen Installieren fehlte das -i. Mit dem folgenden sollte es klappen.

Code: Alles auswählen

 
opsi-package-manager -i opsi-client-agent_4.0.1-6.opsi

Gruß,
Thomas

[d.oertel]

Hi,

wäre doch was für:
http://uib.de/www/service_support/support/index.html

gruss
d.oertel

[lordbernd]

Hi,

danke für die raschen Antworten!

@othiman: Du hattest recht Mit dem -i hat sich der Client Agent installieren lassen.

Jetzt hab ich dafür das Problem:

Code: Alles auswählen

Host:/opt/pcbin/install/opsi-client-agent# ./opsi-deploy-client-agent -vv -x -r -u "adminuser" 192.168.224.75
Password:
[info] * BackendManager is creating BackendDispatcher
[info] Backend context was set to <OPSI.Backend.BackendManager.BackendManager instance at 0x1cc4950>
[info] Loading dispatch config file '/etc/opsi/backendManager/dispatch.conf'
[info] Loading backend config '/etc/opsi/backends/file.conf'
[info] Backend context was set to <OPSI.Backend.BackendManager.BackendDispatcher instance at 0x1cc4998>
[info] Loading backend config '/etc/opsi/backends/opsipxeconfd.conf'
[info] Backend context was set to <OPSI.Backend.BackendManager.BackendDispatcher instance at 0x1cc4998>
[info] * BackendManager is creating ExtendedConfigDataBackend
[info] Setting context to backend <OPSI.Backend.Backend.ExtendedConfigDataBackend instance at 0x1cc47e8>
[notice] Starting deployment to host '192.168.224.75'
[notice] Querying for ip address of host '192.168.224.75'
[info] Getting host '192.168.224.75' by name
[notice] Got ip address '192.168.224.75' from syscall
[notice] Pinging host 192.168.224.75 ...
[info] Executing: ping -q -c2 192.168.224.75
[info] Using encoding 'UTF-8'
[notice] Host 192.168.224.75 is up
[notice] Getting hardware ethernet address of host '192.168.224.75'
[notice] Found hardware ethernet address '78:2b:cb:9c:11:45'
[notice] Creating client '192.168.224.75'
[info] Creating host '<OpsiClient id '192.168.224.75'>'
[notice] Mounting c$ share
[info] Executing: /bin/mount -t cifs -o'username=adminuser,password=*** confidential ***' //192/c$ /tmp/mnt_a9qTINnfmQ
[info] Using encoding 'UTF-8'
[info] Failed to mount clients c$ share: Command '/bin/mount -t cifs -o'username=adminuser,password=*** confidential ***' //192/c$ /tmp/mnt_a9qTINnfmQ' failed (32):
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs), retrying with port 139
[info] Executing: /bin/mount -t cifs -o'port=139,username=adminuser,password=*** confidential ***' //192/c$ /tmp/mnt_a9qTINnfmQ
[info] Using encoding 'UTF-8'
[error] Deployment to '192.168.224.75' failed: Failed to mount c$ share: Command '/bin/mount -t cifs -o'port=139,username=adminuser,password=*** confidential ***' //192/c$ /tmp/mnt_a9qTINnfmQ' failed (32):
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Perhaps you have to disable the firewall or simple file sharing on the windows machine (folder options)?

Wie man sieht, schneidet er die IP einfach nach dem ersten Punkt ab. Das gleiche tritt auch auf, wenn ich die IP in "" setze.

Die Namensauflösung beim Client-Agent deployment funktioniert auch nicht. Ohne Hosts Eintrag wird der Host nicht aufgelöst:

Code: Alles auswählen

Host:/opt/pcbin/install/opsi-client-agent# ./opsi-deploy-client-agent -vv -x -r -u "adminuser" hostname01
Password:
[info] * BackendManager is creating BackendDispatcher
[info] Backend context was set to <OPSI.Backend.BackendManager.BackendManager instance at 0x2bca950>
[info] Loading dispatch config file '/etc/opsi/backendManager/dispatch.conf'
[info] Loading backend config '/etc/opsi/backends/file.conf'
[info] Backend context was set to <OPSI.Backend.BackendManager.BackendDispatcher instance at 0x2bca998>
[info] Loading backend config '/etc/opsi/backends/opsipxeconfd.conf'
[info] Backend context was set to <OPSI.Backend.BackendManager.BackendDispatcher instance at 0x2bca998>
[info] * BackendManager is creating ExtendedConfigDataBackend
[info] Setting context to backend <OPSI.Backend.Backend.ExtendedConfigDataBackend instance at 0x2bca7e8>
[notice] Starting deployment to host 'hostname01.domain.local'
[notice] Querying for ip address of host 'hostname01.domain.local'
[info] Getting host 'hostname01.domain.local' by name
[warning] Failed to get ip address for host 'hostname01.domain.local' by syscall: [Errno -2] Name or service not known
[info] Executing 'nmblookup hostname01#20'
[info] Executing: nmblookup hostname01#20
[info] Using encoding 'UTF-8'
[error] Deployment to 'hostname01.domain.local' failed: Failed to get ip address for host 'hostname01'

Darum habe ich versucht, einen Hosts Eintrag zu erstellen und mit dem Hostnamen zu deployen. Es fängt super an, endet dann aber durch ein Timeout:

Code: Alles auswählen

Host:/opt/pcbin/install/opsi-client-agent# ./opsi-deploy-client-agent -vv -x -r -u "adminuser" hostname01
Password:
[info] * BackendManager is creating BackendDispatcher
[info] Backend context was set to <OPSI.Backend.BackendManager.BackendManager instance at 0x2ea5950>
[info] Loading dispatch config file '/etc/opsi/backendManager/dispatch.conf'
[info] Loading backend config '/etc/opsi/backends/file.conf'
[info] Backend context was set to <OPSI.Backend.BackendManager.BackendDispatcher instance at 0x2ea5998>
[info] Loading backend config '/etc/opsi/backends/opsipxeconfd.conf'
[info] Backend context was set to <OPSI.Backend.BackendManager.BackendDispatcher instance at 0x2ea5998>
[info] * BackendManager is creating ExtendedConfigDataBackend
[info] Setting context to backend <OPSI.Backend.Backend.ExtendedConfigDataBackend instance at 0x2ea57e8>
[notice] Starting deployment to host 'hostname01.domain.local'
[notice] Querying for ip address of host 'hostname01.domain.local'
[info] Getting host 'hostname01.domain.local' by name
[notice] Got ip address '192.168.224.75' from syscall
[notice] Pinging host 192.168.224.75 ...
[info] Executing: ping -q -c2 192.168.224.75
[info] Using encoding 'UTF-8'
[notice] Host 192.168.224.75 is up
[notice] Getting hardware ethernet address of host 'hostname01.domain.local'
[notice] Found hardware ethernet address '78:2b:cb:9c:11:45'
[notice] Creating client 'hostname01.domain.local'
[info] Creating host '<OpsiClient id 'hostname01.domain.local'>'
[notice] Mounting c$ share
[info] Executing: /bin/mount -t cifs -o'username=adminuser,password=*** confidential ***' //hostname01/c$ /tmp/mnt_89IEFhAiCR
[info] Using encoding 'UTF-8'
[info] Failed to mount clients c$ share: Command '/bin/mount -t cifs -o'username=adminuser,password=*** confidential ***' //hostname01/c$ /tmp/mnt_89IEFhAiCR' failed (32):
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs), retrying with port 139
[info] Executing: /bin/mount -t cifs -o'port=139,username=adminuser,password=*** confidential ***' //hostname01/c$ /tmp/mnt_89IEFhAiCR
[info] Using encoding 'UTF-8'
[error] Deployment to 'hostname01.domain.local' failed: Failed to mount c$ share: Command '/bin/mount -t cifs -o'port=139,username=adminuser,password=*** confidential ***' //hostname01/c$ /tmp/mnt_89IEFhAiCR' timed out atfer 15 seconds
Perhaps you have to disable the firewall or simple file sharing on the windows machine (folder options)?

Warum kann ich seit dem Update keine Opsi-Client-Agents über den Hostnamen deployen? Die Namensauflösung funktioniert zb. mit Ping normal... auch ohne Hosts Eintrag.

Hat das gleiche Problem noch jemand? Was habt ihr für einen Workaround dafür?

LG,
Bernd

[j.schneider]

Hallo,

definitiv ein Problem mit der Namensauflösung.
Bitte einmal die /etc/nsswitch.conf posten.
Es könnte mit Squeeze ein mdns4-Eintrag hinzugekommen sein.

Gruß,
Jan Schneider

[lordbernd]

Hi,

danke für deine Antwort.

Das mit mdns4 hab ich schon wo gelesen und hab es daher deaktiviert. Der Eintrag ist aber nach dem Update neu dazu gekommen.

nsswitch.conf:

Code: Alles auswählen

# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.

passwd:         compat
group:          compat
shadow:         compat

#hosts:          files dns mdns4_minimal mdns4
hosts:          files dns
networks:       files

protocols:      db files
services:       db files
ethers:         db files
rpc:            db files

netgroup:       nis

LG,
Bernd

[j.schneider]

Bitte einmal die Option "-c" versuchen.

[lordbernd]

Hi,

hab ich auch versucht, jedoch kommt wieder das gleiche:

Code: Alles auswählen

Host:/opt/pcbin/install/opsi-client-agent# ./opsi-deploy-client-agent -vv -x -c -r -u "adminuser" hostname
Password:
[info] * BackendManager is creating BackendDispatcher
[info] Backend context was set to <OPSI.Backend.BackendManager.BackendManager instance at 0x2509950>
[info] Loading dispatch config file '/etc/opsi/backendManager/dispatch.conf'
[info] Loading backend config '/etc/opsi/backends/file.conf'
[info] Backend context was set to <OPSI.Backend.BackendManager.BackendDispatcher instance at 0x2509998>
[info] Loading backend config '/etc/opsi/backends/opsipxeconfd.conf'
[info] Backend context was set to <OPSI.Backend.BackendManager.BackendDispatcher instance at 0x2509998>
[info] * BackendManager is creating ExtendedConfigDataBackend
[info] Setting context to backend <OPSI.Backend.Backend.ExtendedConfigDataBackend instance at 0x25097e8>
[notice] Starting deployment to host 'hostname.domain.local'
[notice] Querying for ip address of host 'hostname.domain.local'
[info] Getting host 'hostname.domain.local' by name
[notice] Got ip address '192.168.224.75' from syscall
[notice] Pinging host 192.168.224.75 ...
[info] Executing: ping -q -c2 192.168.224.75
[info] Using encoding 'UTF-8'
[notice] Host 192.168.224.75 is up
[notice] Getting hardware ethernet address of host 'hostname.domain.local'
[notice] Found hardware ethernet address '78:2b:cb:9c:11:45'
[notice] Creating client 'hostname.domain.local'
[info] Creating host '<OpsiClient id 'hostname.domain.local'>'
[notice] Mounting c$ share
[info] Executing: /bin/mount -t cifs -o'username=adminuser,password=*** confidential ***' //hostname.domain.local/c$ /tmp/mnt_NU4q5r9XuS
[info] Using encoding 'UTF-8'
[info] Failed to mount clients c$ share: Command '/bin/mount -t cifs -o'username=adminuser,password=*** confidential ***' //hostname.domain.local/c$ /tmp/mnt_NU4q5r9XuS' failed (32):
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs), retrying with port 139
[info] Executing: /bin/mount -t cifs -o'port=139,username=adminuser,password=*** confidential ***' //hostname.domain.local/c$ /tmp/mnt_NU4q5r9XuS
[info] Using encoding 'UTF-8'
[error] Deployment to 'hostname.domain.local' failed: Failed to mount c$ share: Command '/bin/mount -t cifs -o'port=139,username=adminuser,password=*** confidential ***' //hostname.domain.local/c$ /tmp/mnt_NU4q5r9XuS' timed out atfer 15 seconds
Perhaps you have to disable the firewall or simple file sharing on the windows machine (folder options)?

Firewall und einfache Dateifreigabe sind "abgedreht".

LG,
Bernd