VMware Cloud Community
ghaithsultaneh
Contributor
Contributor

VRO No logs found

Hi all ,

I am Using VRO 7.3.1 and there i can't see any output for any workflow . the logs are always empty .

'no logs found' .

I tried to make a simple workflow which print the word 'Hello' . and nothing appears in the logs too.

so how can i make my results appear in the logs?

thanks

0 Kudos
7 Replies
daphnissov
Immortal
Immortal

Show your code, then we'll know.

0 Kudos
ghaithsultaneh
Contributor
Contributor

1.png

0 Kudos
ghaithsultaneh
Contributor
Contributor

as you can see in the picture , and there is no output in the logs.

0 Kudos
daphnissov
Immortal
Immortal

You aren't showing the log so I can't see anything. Show a completed workflow run.

0 Kudos
ghaithsultaneh
Contributor
Contributor

2.png

0 Kudos
qc4vmware
Virtuoso
Virtuoso

Take a look at these KB's.  I've run into both situations.

VMware Knowledge Base

This is a bit older but I've hit it

    1. In the log pane of the Orchestrator client you cannot see debug log messages for the workflow token.
      Workaround: Update the log level for the scripting logs.
      1. Use ssh into the Orchestrator appliance and log in as root.
      2. Open the /etc/vco/app-server/log4j.xml file with a text editor.
      3. Change the log level by updating:
      4. <category additivity="false" name="SCRIPTING_LOG">
        <priority value="INFO"/>
      5. to
      6. <category additivity="false" name="SCRIPTING_LOG">
        <priority value="DEBUG"/>
kaushikpal
Contributor
Contributor

First Check: 1. Login into the appliances using root and run the command df -h to check if the disks are full or not.

                      2. If they are you need to increase the space and then check running the workflow again. It is possible that the disk is full so logs are not being written to the server.

If not this case.

Second Check: 1. Login to vco control center and navigate to configure logs.

                           2. Check if the Log Level is set to info and Scripting Log Level is set to Debug.

I think this might resolve your problem. If not do let me know.

0 Kudos