Hi everyone,
I am currently testing the Vix plug-in in vCO. I found that both Run program in guest and Run script in guest workflow work properly in Windows guest. But for the Linux guest. The workflow run to complete without throwing any exception. Actually, nothing change in the guest.
I can delete file in guest using the same credential, so I guess this issue is not related to access right.
Regards,
Karen
Hi!
(Again, no solution :smileyblush:, only further testing ideas...)
Can you try to do the task manually leveraging the VIX API directly (via vmrun.exe)?
So we can figure out if it's a problem of VIX in general (then cross-posting it in the VIX-community may be an idea), or if it's an issue only of the vCO-Plugin.
Regards,
Joerg
Hi
I just found in the log when I run the workflow.
Oct 7 17:27:07 localhost vmtoolsd: PAM unable to dlopen(/lib/security/pam_unix2.so)
Oct 7 17:27:07 localhost vmtoolsd: PAM [error: /lib/security/pam_unix2.so: cannot open shared object file: No such file or directory]
Oct 7 17:27:07 localhost vmtoolsd: PAM adding faulty module: /lib/security/pam_unix2.so
Oct 7 17:27:07 localhost vmtoolsd: PAM unable to dlopen(/lib/security/pam_unix2.so)
Oct 7 17:27:07 localhost vmtoolsd: PAM [error: /lib/security/pam_unix2.so: cannot open shared object file: No such file or directory]
Oct 7 17:27:07 localhost vmtoolsd: PAM adding faulty module: /lib/security/pam_unix2.so
Oct 7 17:27:08 localhost vmtoolsd: PAM unable to dlopen(/lib/security/pam_unix2.so)
Oct 7 17:27:08 localhost vmtoolsd: PAM [error: /lib/security/pam_unix2.so: cannot open shared object file: No such file or directory]
Oct 7 17:27:08 localhost vmtoolsd: PAM adding faulty module: /lib/security/pam_unix2.so
Regards,
Karen
ok. This points away from the Plugin to a general issue with the VIX-API. You should shift your research in this direction, a starting point might be:
You could also use the SSH plug-in to start scripts and programs on remote Linux machines.