Jira (FACT-2631) Trace is not working as expected
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2631 Trace is not working as expected Change By: Bogdan Irimie Log level was set incorrectly to `trace` when calling the `trace` API method. The `trace` API method should enable backtrace. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359512.1590061804000.68205.1590130080291%40Atlassian.JIRA.
Jira (FACT-2631) Trace is not working as expected
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2631
Trace is not working as expected
Change By:
Bogdan Irimie
*Puppet Version:* *Puppet Server Version:* *OS Name/Version:*Describe your issue in as much detail as possible… Describe steps to reproduce…*Desired Behavior:**Actual Behavior:*Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.Examples: Run puppet agent with --test --trace --debugRelevant sections of {{/var/log/puppetlabs/puppetserver/puppetserver.log}} or any applicable logs from the same directory.For more detailed information turn up the server logs by upping the log level in the server's logback.xmlRelevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig)For memory issues with server heap dumps are also helpful.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the
Jira (FACT-2631) Trace is not working as expected
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2631 Trace is not working as expected Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.359512.1590061804000.67463.1590063900042%40Atlassian.JIRA.
Jira (FACT-2631) Trace is not working as expected
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2631 Trace is not working as expected Issue Type: Bug Assignee: Unassigned Created: 2020/05/21 4:50 AM Priority: Normal Reporter: Bogdan Irimie Puppet Version: Puppet Server Version: OS Name/Version: Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful. Add Comment
