#1119: command line option --trace does not provide backtrace
------------------------+---------------------------------------------------
Reporter: jtimberman | Owner: community
Type: defect | Status: new
Priority: normal | Milestone:
Component: client | Version: 0.24.2
Severity: normal | Resolution:
Keywords: trace | Stage: Unreviewed
Patch: None | Complexity: Unknown
------------------------+---------------------------------------------------
Old description:
> I'm trying to troubleshoot a problem, and I don't get any backtrace from
> puppetd --test --trace:
>
> web1b:/var/spool/repackage
> $ sudo puppetd --test
> notice: Ignoring cache
> err: Could not retrieve catalog: undefined method `scope' for
> nil:NilClass at /var/lib/puppet/master/manifests/nodetype.pp:333 on node
> web1b
> warning: Not using cache on failed catalog
> web1b:/var/spool/repackage
> $ sudo puppetd --test --trace
> notice: Ignoring cache
> err: Could not retrieve catalog: undefined method `scope' for
> nil:NilClass at /var/lib/puppet/master/manifests/nodetype.pp:333 on node
> web1b
> warning: Not using cache on failed catalog
>
> This is on a CentOS 5.1 system with puppet 0.24.2 installed from dlutter
> yum repo, package puppet-0.24.2-1.el5.
>
> Also opening a bug on the above error message, as it did not occur with
> 0.24.1.
New description:
I'm trying to troubleshoot a problem, and I don't get any backtrace from
puppetd --test --trace:
{{{
web1b:/var/spool/repackage
$ sudo puppetd --test
notice: Ignoring cache
err: Could not retrieve catalog: undefined method `scope' for nil:NilClass
at /var/lib/puppet/master/manifests/nodetype.pp:333 on node web1b
warning: Not using cache on failed catalog
web1b:/var/spool/repackage
$ sudo puppetd --test --trace
notice: Ignoring cache
err: Could not retrieve catalog: undefined method `scope' for nil:NilClass
at /var/lib/puppet/master/manifests/nodetype.pp:333 on node web1b
warning: Not using cache on failed catalog
}}}
This is on a CentOS 5.1 system with puppet 0.24.2 installed from dlutter
yum repo, package puppet-0.24.2-1.el5.
Also opening a bug on the above error message, as it did not occur with
0.24.1.
Comment (by DavidS):
fixed formatting markup;
Aw, shucks! I was helping out on this one on IRC yesterday, and forgot the
most important part! This could very well be a Exception from the server,
so to see the backtrace, the puppetmaster would have to run under --trace
too.
--
Ticket URL: <http://reductivelabs.com/trac/puppet/ticket/1119#comment:1>
puppet <http://reductivelabs.com>
Puppet - Portable System Automation
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
