Katwood
Contributor
Contributor

Workflow log...

vCO 5,1 w/client, wondering what happened to the log for a specific workflow that has run:

Server.log -> Workflow Events

System.log -> vCO Log, info

System.debug -> vCO Log, debug

What's the scoop on logs for workflows?

0 Kudos
9 Replies
cdecanini_
VMware Employee
VMware Employee

Sorry but I am not sure I get the question right. What is the problem ?

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
0 Kudos
Katwood
Contributor
Contributor

Script.PNG

Empty.PNG

0 Kudos
dimitrovg
VMware Employee
VMware Employee

Did you start the vCO client after the System.log() was executed? The logs in the client are shown only if the client is running when they are written. Otherwise you can see them in the server.log file. About the Server.log() the message goes to the DB and is not printed in the server.log nor in the client.

0 Kudos
Katwood
Contributor
Contributor

Client open, workflow run, nothing in the specific workflow log, need to goto events for the workflow or VCO server logs.

0 Kudos
dimitrovg
VMware Employee
VMware Employee

Hm, I will try to reproduce it. Is the vco server running on windows or do you use appliance? How did you start the client as standalone or do you use the Java Web Start? What OS the client runs?

Can you send me the client and the server logs?

If you installed the client under Windows the log is located at C:\Program Files\VMware\Orchestrator\apps\vso.log

0 Kudos
Katwood
Contributor
Contributor

VCO is Windows.

Client is run Standalone.

Win7X64

VCO Server log:

2012-09-13 08:47:21.735-0700 INFO  [WorkflowHandler] ADInfo
2012-09-13 08:49:40.856-0700 INFO  [SecurityTokenServiceImpl] Successfully acquired token for user: administrator
2012-09-13 08:49:41.027-0700 INFO  [SecurityTokenServiceImpl] Successfully acquired token for user: {Name: Administrator, Domain: VC}
2012-09-13 08:49:41.059-0700 INFO  [Execution] Executing workflow 'ADInfo'
2012-09-13 08:49:41.152-0700 INFO  [SCRIPTING_LOG] [ADInfo (9/13/12 08:49:41)] system log
2012-09-13 08:49:41.152-0700 DEBUG [SCRIPTING_LOG] [ADInfo (9/13/12 08:49:41)] system debug
2012-09-13 08:49:41.277-0700 INFO  [WorkflowHandler] ADInfo
0 Kudos
cdecanini_
VMware Employee
VMware Employee

OK, the system.log is not printing. I have got the same issue using the vCO appliance and the MacOS installable client or the java web start one. I found this out yesterday and wanted to investigate further.

Definitely something to look at. Glad George D is already doing it.

Christophe.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
0 Kudos
IvanKarastoyano
Contributor
Contributor

I guess the difference between the clocks on the machine where VCO client runs and VCO Appliance's machine is bigger than 10 min. This causes the messages to be considered expired. Is it possible to check the two clocks are synchronized?

0 Kudos
cdecanini_
VMware Employee
VMware Employee

Hi Ivan,

I think you nailed it. This was the case for me and explains why I have never got this problem when running the client & server in the same host.

Thanks.

Christophe.

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vCenter Orchestrator tips and tutorials - @vCOTeam on Twitter
0 Kudos