Routing to Syslog

[admin]

Apparently there has been a change between VCO 5.1.0 build 2725 and 5.1.1 build 2942.

In the 5.1.0 build I am able to forward my log messages to syslog by making a modification to the syslog-ng.conf file and modifying the log4j.xml file.  In the 5.1.1 build my log messages will no longer forward.

Can someone tell me what additional configuration changes are required to route my messages to syslog?

[tschoergez]

can you check if the update overwrote your complete log4j.xml file?

So you have to redo all the settings there manually.

Cheers,

Joerg

Von: sbryan77

Gesendet: Mittwoch, 22. Mai 2013 18:18

An: Joerg Lew

Betreff: New message: "Routing to Syslog"

VMware Communities<http://communities.vmware.com/index.jspa>

Routing to Syslog

created by sbryan77<http://communities.vmware.com/people/sbryan77> in Orchestrator - View the full discussion<http://communities.vmware.com/message/2242966#2242966>

[admin]

I checked my log4j.xml file and my modifications are in it.  I am aware that when I make a change to this file I need to tail the server.log and wait for the message indicating the properties file has been reloaded.  I am also aware if I make a modification in the Web view to the configuration it will overwrite this file.

This works fine in my 5.1.0 instance but does not work in 5.1.1.

[tschoergez]

hmmmm, what else could be new in 5.1.1?

Firewall settings, (maybe even on the syslog server, if your 5.1.1 has another IP)...

Syslog configuration on the server, just accepting incoming messages from the old instance...

Are you using the Appliance or a windows based vCO? If Appliance, you could try to send them to the local syslog service to rule out networking issues.

Cheers,

Joerg

Von: sbryan77

Gesendet: Mittwoch, 22. Mai 2013 20:27

An: Joerg Lew

Betreff: New message: "Routing to Syslog"

VMware Communities<http://communities.vmware.com/index.jspa>

Routing to Syslog

created by sbryan77<http://communities.vmware.com/people/sbryan77> in Orchestrator - View the full discussion<http://communities.vmware.com/message/2243036#2243036>

[admin]

I am using the appliance and I am trying to send it to the local syslog.  This is what I am doing on the 5.1.0 appliance and it sends to the local syslog with no issue.  I am doing it by IP address in both cases.

I did notice on the 5.1.1 install that I was able to install it with a unique host name so it does not default to localhost.localdom.  I checked the /etc/hosts file and it does have the host name that I assigned, but I don't know how that could impact logging.  I also notice in my VCO client when I make the changes to route to syslog I no longer get any messages in my console window.  This is not the behavior I get in 5.1.0  In the previous release I get messages in my console and get messages in my syslog.

[tschoergez]

(I don’t have access to a 5.1.1 lab to reproduce, so all guesswork here)

can you compare the syslogd settings of both instances? perhaps for security reasons they use different default settings.

http://stackoverflow.com/questions/12490253/syslogappender-not-working

Von: sbryan77

Gesendet: Mittwoch, 22. Mai 2013 21:38

An: Joerg Lew

Betreff: New message: "Routing to Syslog"

VMware Communities<http://communities.vmware.com/index.jspa>

Routing to Syslog

created by sbryan77<http://communities.vmware.com/people/sbryan77> in Orchestrator - View the full discussion<http://communities.vmware.com/message/2243039#2243039>

[admin]

I have done a diff on the syslog-ng.conf files and they are identical.  The only modification I made was to allow udp network traffic.

On thing I do see in the 5.1.1 syslog when I kick off a workflow is:

warning: /etc/hosts.allow, line 66: host name mismatch: vcovcops != (null) (::ffff:127.0.0.1)

I just now created a new 5.1.1 instance from the same ovf file and I do notice that when I run a workflow with system.log and server.log statements in it nothing is showing in the logs tab of the vco client.  In the past all log values show in this tab.  The log values are being logged to the script-log.log and server.log files.  It appears to me that there have been changes to logging in general to have changed this behavior in the vco client.  Are there any new settings that have to be modified?

[cdecanini_]

It may not be relevant but could you check that if you time synchronize the client and the server the logs show up in the client ? This is a common issue.

[admin]

I am doing the forward to syslog on the same machine as where the vco server is running. I don't think there is any time synchronization to consider.  If there is an additional time sync of some sort I need to perform can you provide me further details on how to do that?