Jira (PUP-8729) Puppet does not accept UTF8 on the command line
Title: Message Title Josh Cooper commented on PUP-8729 Re: Puppet does not accept UTF8 on the command line Adding fix version on this so we validate Ruby 3 on Windows handles UTF-8 command line arguments correctly. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.128358.1461692616000.1836.1648516860141%40Atlassian.JIRA.
Jira (PUP-8729) Puppet does not accept UTF8 on the command line
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8729 Puppet does not accept UTF8 on the command line Change By: Josh Cooper Fix Version/s: PUP 8.0.0 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.128358.1461692616000.1833.1648516800038%40Atlassian.JIRA.
Jira (FACT-1577) Provide a stable ABI/SONAME
Title: Message Title Josh Cooper commented on FACT-1577 Re: Provide a stable ABI/SONAME Given facter was rewritten in ruby, we don't have plans on implementing this for facter 3. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.176815.1487978719000.1832.1648516740025%40Atlassian.JIRA.
Jira (FACT-1501) timezone contains wrong value
Title: Message Title
Josh Cooper commented on FACT-1501
Re: timezone contains wrong value
This issue is because the timezone fact relies on Time.now.strftime("%Z") and Windows just behaves differently on Windows:
C:\ProgramData\PuppetLabs>ruby.exe -e 'puts Time.now.strftime("%Z")'
Pacific Daylight Time
Given that facter has behaved this way for so long and that timezone identifiers are inherently ambiguous
'CST' means one thing in China and something else in North America, and 'IST' can refer to time in India, Ireland or Israel.
I'm going to close this as won't fix.
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
--
You received this message
Jira (PUP-7126) Selinux.matchpathcon is deprecated, use selabel_lookup instead
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7126 Selinux.matchpathcon is deprecated, use selabel_lookup instead Change By: Josh Cooper Summary: Selinux.matchpathcon is deprecated , use selabel_lookup instead Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.171401.1485103984000.1804.1648513740040%40Atlassian.JIRA.
Jira (PUP-11473) Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Title: Message Title Austin Boyd updated an issue Puppet / PUP-11473 Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016 Change By: Austin Boyd Zendesk Ticket Count: 1 Zendesk Ticket IDs: 47445 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.437686.1646195359000.1794.1648512720105%40Atlassian.JIRA.
Jira (PUP-11473) Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Title: Message Title Austin Boyd updated an issue Puppet / PUP-11473 Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016 Change By: Austin Boyd Labels: jira_escalated Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.437686.1646195359000.1795.1648512720173%40Atlassian.JIRA.
Jira (PUP-11473) Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016
Title: Message Title Josh Cooper commented on PUP-11473 Re: Error: Failed to apply catalog: undefined method `bytesize' for nil:NilClass on WinServer 2016 selvakumar.subburaj If the problem persists, please try running the following and attaching the output: C:\> icacls C:\ProgramData\PuppetLabs\puppet\cache\state\last_run_report.yaml Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.437686.1646195359000.1600.1648499940174%40Atlassian.JIRA.
Jira (PUP-11446) Facts returning nil are converted to empty string
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11446 Facts returning nil are converted to empty string Change By: Josh Cooper Sprint: Phoenix 2022-04-13 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.433923.1643832932000.1593.1648499400081%40Atlassian.JIRA.
Jira (FACT-3109) Failed to get networking information: "\xE5" to UTF-8 in conversion from ASCII-8BIT to UTF-8 to UTF-16LE
Title: Message Title Josh Cooper commented on FACT-3109 Re: Failed to get networking information: "\xE5" to UTF-8 in conversion from ASCII-8BIT to UTF-8 to UTF-16LE The error occurs when trying to read the "Friendly Name" for the interface. In Facter 3.x we used to do net_interface.name = boost::nowide::narrow(pCurAddr->FriendlyName); The boost libraries automatically convert the wide string friendly name to UTF-8 and most importantly they https://www.boost.org/doc/libs/develop/libs/nowide/doc/html/index.html If there are non-UTF-8 characters in the passed string, the conversion will replace them by a replacement character (default: U+FFFD) similar to what the NT kernel does. Since the "friendly name" is user editable, it's possible for the data to be incorrectly encoded (usually it's encoded based on the current code page instead of UTF-16LE). We should ensure we replace invalid chars when reading the friendly name. 1. Update facter's read_wide_string_without_length method to accept an optional argument to replace invalid chars. If set, call: str.encode(Encoding::UTF_8, str.encoding, replace: invalid) 2. Update networking.rb to pass the optional argument We already do something like this in puppet when reading garbage from the registry. See https://github.com/puppetlabs/puppet/blob/1b8c8a13b9e87ad12cf8452aade7c2ead0e34edc/lib/puppet/ffi/windows/api_types.rb#L53 Add Comment
Jira (PUP-11478) puppet server mount points do not follow symlinks
Title: Message Title Jason Grammenos commented on PUP-11478 Re: puppet server mount points do not follow symlinks thanks josh for clarify my mistake in not setting the links=> follow parameter Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.440878.1647624693000.1578.1648497720063%40Atlassian.JIRA.
Jira (PUP-11478) puppet server mount points do not follow symlinks
Title: Message Title
Josh Cooper commented on PUP-11478
Re: puppet server mount points do not follow symlinks
Puppet's behavior with symlinks depends on the ensure property and links parameter, see https://puppet.com/docs/puppet/6/types/file.html#file-attribute-links. In order to have puppet agent follow the link, you'll need to set:
file { '/path/to/file.v5':
ensure => file
mode=> '0775',
links => follow,
source => 'puppet:///installation_files/path/to/actual_file.v5',
}
Add Comment
This message
Jira (PUP-11480) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Josh Cooper commented on PUP-11480 Re: Corrective Change YAML file causes errors when type parameter is a complex type The mysql issue was fixed in https://github.com/puppetlabs/puppetlabs-mysql/pull/1429 though it looks like fix hasn't been released yet. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.441197.164805035.1570.1648497240177%40Atlassian.JIRA.
Jira (PUP-11474) puppet run after agent upgrade when use_cached_catalog is enabled results in error
Title: Message Title Josh Cooper commented on PUP-11474 Re: puppet run after agent upgrade when use_cached_catalog is enabled results in error We decided to close this given it only occurs once and automatically resolves itself when the agent next runs. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.437744.1646254789000.1560.1648496640138%40Atlassian.JIRA.
Jira (PUP-11451) Make collecting exported resources optional
Title: Message Title
Nacho Barrientos commented on PUP-11451
Re: Make collecting exported resources optional
Thinking twice for us it'd be even better to stop the compilation than just collecting "nothing". Something like this seems to work:
require 'puppet/indirector/none'
class Puppet::Resource::Fail < Puppet::Indirector::None
def find(request)
raise Puppet::Indirector::ValidationError, _("Collecting exported resources is disabled.")
end
def search(request)
raise Puppet::Indirector::ValidationError, _("Collecting exported resources is disabled.")
end
end
which would result in something like:
Jira (PDB-5469) PuppetDB services shutting down due to query performance
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-5469 PuppetDB services shutting down due to query performance Change By: Austin Boyd Zendesk Ticket Count: 1 Zendesk Ticket IDs: 47705 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.441921.1648448076000.786.164844972%40Atlassian.JIRA.
Jira (PDB-5469) PuppetDB services shutting down due to query performance
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-5469 PuppetDB services shutting down due to query performance Change By: Austin Boyd Labels: jira_escalated Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.441921.1648448076000.787.164844999%40Atlassian.JIRA.
Jira (PDB-5469) PuppetDB services shutting down due to query performance
Title: Message Title
Selvakumar Azhagarsami updated an issue
PuppetDB / PDB-5469
PuppetDB services shutting down due to query performance
Change By:
Selvakumar Azhagarsami
h3. Summary:The issue reported on running the node query with 50 nodes, it got failed with the console error "Error resolving pql query" The query used was an arbitrary selection of 50 nodes using the OR condition.h5. Did it ever work?It worked for 20 nodes and in the case of 50 nodes, it got failed with the PQL error.h5. When did the issue first occur?Not sure. The customer reported this issue as a possible bug.h5. If applicable, did you do a run with --debug --trace?N/Ah4. OS & Version: Ubuntu- 18.04.6 LTS (Bionic Beaver) h4. PE Version on the affected machine:2021.5h4. Master Or Agent Affected:Masterh4. All In One Or Split Install:Split installh4. Steps Taken To Reproduce:The customer has provided the below steps to reproduce this error1. Perform an expensive PQL query from the console. In our case, we were able to reproduce the problem with 30+ OR statements in a query: {code:java} inventory[certname] \ { certname ~ "bastion-i-0df61833aa00e6acc" or certname ~ "compile-master-i-05d0fd872d2b1964f" or certname ~ "compile-master-i-061f9a63122235787"} {code} (and so on, of course, with 30+ nodes)2. There is no step 2! When running this query, I get the error in the console "Error resolving pql query: Server Error". It appears that the UI timeout occurs after 60 seconds, and the user would have no idea they caused a problem.On the backend, PuppetDB queries start getting slower and slower, and the load on the server in question climbs. In at least one test, if left unchecked, the load runs away and `apport` runs to try to gather a crash dump. {code:java}// 2022-03-10T17:26:59.813Z WARN [p.p.h.query] Parsing PQL took 3,705.52 ms: "nodes[certname] { report_timestamp > \"2022-03-01T00:00:00Z\" }" 2022-03-10T17:27:05.470Z WARN [p.p.h.query] Parsing PQL took 9,362.058 ms: "resources[certname] {\n type = 'Class' and\n title = 'Puppet_enterprise::Profile::Master' and\n nodes{ deactivated is null and expired is null }\n order by certname\n }" {code} Files Acquired:Support Bundle from Primary master and external puppet database h4. Relevant Error Messages:We can see the following error in the puppetdb logs which is matching with the customer who has tried to execute the query. {code:java}// error from the puppetdb Log at java.base/java.lang.Thread.run(Thread.java:829)2022-03-10T17:42:47.401Z INFO [p.p.c.services] Periodic activities halted2022-03-10T17:42:47.402Z INFO [c.z.h.HikariDataSource] PDBWritePool - Shutdown initiated...2022-03-10T17:43:03.587Z ERROR [p.p.threadpool] Reporting unexpected error from thread cmd-proc-thread-392 to stderr and logjava.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@7294c26[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@22c31f38[Wrapped task =
Jira (PDB-5469) PuppetDB services shutting down due to query performance
Title: Message Title Subramanian Kalidass commented on PDB-5469 Re: PuppetDB services shutting down due to query performance This issue is a clone of PE-33705 for the sake of customer viewing and support ticket closure. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.441921.1648448076000.785.1648448700094%40Atlassian.JIRA.
Jira (PDB-5469) PuppetDB services shutting down due to query performance
Title: Message Title
Subramanian Kalidass updated an issue
PuppetDB / PDB-5469
PuppetDB services shutting down due to query performance
Change By:
Subramanian Kalidass
h3. Summary:The customer reported the issue reported on running the node query with 50 nodes, it got failed with the console error "Error resolving pql query" The query used was an arbitrary selection of 50 nodes using the OR condition.h5. Did it ever work?It worked for 20 nodes and in the case of 50 nodes, it got failed with the PQL error.h5. When did the issue first occur?Not sure. The customer reported this issue as a possible bug.h5. If applicable, did you do a run with --debug --trace?N/Ah4. OS & Version: Ubuntu- 18.04.6 LTS (Bionic Beaver) h4. PE Version on the affected machine:2021.5h4. Master Or Agent Affected:Masterh4. All In One Or Split Install:Split installh4. Steps Taken To Reproduce:The customer has provided the below steps to reproduce this error1. Perform an expensive PQL query from the console. In our case, we were able to reproduce the problem with 30+ OR statements in a query:inventory[certname] \{ certname ~ "bastion-i-0df61833aa00e6acc" or certname ~ "compile-master-i-05d0fd872d2b1964f" or certname ~ "compile-master-i-061f9a63122235787"}(and so on, of course, with 30+ nodes)2. There is no step 2! When running this query, I get the error in the console "Error resolving pql query: Server Error". It appears that the UI timeout occurs after 60 seconds, and the user would have no idea they caused a problem.On the backend, PuppetDB queries start getting slower and slower, and the load on the server in question climbs. In at least one test, if left unchecked, the load runs away and `apport` runs to try to gather a crash dump. {code:java} // 2022-03-10T17:26:59.813Z WARN [p.p.h.query] Parsing PQL took 3,705.52 ms: "nodes[certname] { report_timestamp > \"2022-03-01T00:00:00Z\" }" 2022-03-10T17:27:05.470Z WARN [p.p.h.query] Parsing PQL took 9,362.058 ms: "resources[certname] {\n type = 'Class' and\n title = 'Puppet_enterprise::Profile::Master' and\n nodes{ deactivated is null and expired is null }\n order by certname\n }" {code} Files Acquired:Support Bundle from Primary master and external puppet database h4. Relevant Error Messages:We can see the following error in the puppetdb logs which is matching with the customer who has tried to execute the query. {code:java} // error from the puppetdb Log at java.base/java.lang.Thread.run(Thread.java:829)2022-03-10T17:42:47.401Z INFO [p.p.c.services] Periodic activities halted2022-03-10T17:42:47.402Z INFO [c.z.h.HikariDataSource] PDBWritePool - Shutdown initiated...2022-03-10T17:43:03.587Z ERROR [p.p.threadpool] Reporting unexpected error from thread cmd-proc-thread-392 to stderr and logjava.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@7294c26[Not completed, task = java.util.concurrent.Executors$RunnableAdapter@22c31f38[Wrapped task =
Jira (PDB-5469) PuppetDB services shutting down due to query performance
Title: Message Title
Subramanian Kalidass updated an issue
PuppetDB / PDB-5469
PuppetDB services shutting down due to query performance
Change By:
Subramanian Kalidass
h3. Summary:The customer reported the issue on running the node query with 50 nodes, it got failed with the console error "Error resolving pql query" The query used was an arbitrary selection of 50 nodes using the OR condition.h5. Customer Organization Name : Splunk Release Engineering h5. Did it ever work? As per the ticket, it It worked for 20 nodes and in the case of 50 nodes, it got failed with the PQL error.h5. When did the issue first occur?Not sure. The customer reported this issue as a possible bug.h5. If applicable, did you do a run with --debug --trace?N/Ah4. OS & Version: Ubuntu- 18.04.6 LTS (Bionic Beaver) h4. PE Version on the affected machine:2021.5h4. Master Or Agent Affected:Masterh4. All In One Or Split Install:Split installh4. Steps Taken To Reproduce:The customer has provided the below steps to reproduce this error1. Perform an expensive PQL query from the console. In our case, we were able to reproduce the problem with 30+ OR statements in a query:inventory[certname] \{ certname ~ "bastion-i-0df61833aa00e6acc" or certname ~ "compile-master-i-05d0fd872d2b1964f" or certname ~ "compile-master-i-061f9a63122235787"}(and so on, of course, with 30+ nodes)2. There is no step 2! When running this query, I get the error in the console "Error resolving pql query: Server Error". It appears that the UI timeout occurs after 60 seconds, and the user would have no idea they caused a problem.On the backend, PuppetDB queries start getting slower and slower, and the load on the server in question climbs. In at least one test, if left unchecked, the load runs away and `apport` runs to try to gather a crash dump. | {code:java} // 2022-03-10T17:26:59.813Z WARN [p.p.h.query] Parsing PQL took 3,705.52 ms: "nodes[certname] \ { report_timestamp > \"2022-03-01T00:00:00Z\" }" 2022-03-10T17:27:05.470Z WARN [p.p.h.query] Parsing PQL took 9,362.058 ms: "resources[certname] {\n type = 'Class' and\n title = 'Puppet_enterprise::Profile::Master' and\n nodes || { deactivated is null and expired is null }\n order by certname\n }" | {code} Files Acquired:Support Bundle from Primary master and external puppet database h4. Relevant Error Messages:We can see the following error in the puppetdb logs which is matching with the customer who has tried to execute the query. | {code:java} // error from the puppetdb Log || at java.base/java.lang.Thread.run(Thread.java:829) || 2022-03-10T17:42:47.401Z INFO [p.p.c.services] Periodic activities halted||2022 halted2022 -03-10T17:42:47.402Z INFO [c.z.h.HikariDataSource] PDBWritePool - Shutdown initiated... || 2022-03-10T17:43:03.587Z ERROR [p.p.threadpool] Reporting unexpected error from thread cmd-proc-thread-392 to stderr and log||java logjava .util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@7294c26[Not completed,
Jira (PDB-5469) PuppetDB services shutting down due to query performance
Title: Message Title
Subramanian Kalidass created an issue
PuppetDB / PDB-5469
PuppetDB services shutting down due to query performance
Issue Type:
Bug
Assignee:
Unassigned
Components:
PuppetDB
Created:
2022/03/27 11:14 PM
Priority:
Normal
Reporter:
Subramanian Kalidass
Summary: The customer reported the issue on running the node query with 50 nodes, it got failed with the console error "Error resolving pql query" The query used was an arbitrary selection of 50 nodes using the OR condition. Customer Organization Name : Splunk Release Engineering Did it ever work? As per the ticket, it worked for 20 nodes and in the case of 50 nodes, it got failed with the PQL error. When did the issue first occur? Not sure. The customer reported this issue as a possible bug. If applicable, did you do a run with --debug --trace? N/A OS & Version: Ubuntu- 18.04.6 LTS (Bionic Beaver) PE Version on affected machine: 2021.5 Master Or Agent Affected: Master All In One Or Split Install: Split install Steps Taken To Reproduce: The customer has provided the below steps to reproduce this error 1. Perform an expensive PQL query from the console. In our case, we were able to reproduce the problem with 30+ OR statements in a query: inventory[certname] { certname ~ "bastion-i-0df61833aa00e6acc" or certname ~ "compile-master-i-05d0fd872d2b1964f" or certname ~ "compile-master-i-061f9a63122235787"} (and so on, of course, with 30+ nodes) 2. There is no step 2! When running this query, I get the error in the console "Error resolving pql query: Server Error". It appears that the UI timeout occurs after 60 seconds, and the user would have no idea they caused a problem. On the backend, PuppetDB queries start getting slower and slower, and the load on the server in question climbs. In at least one test, if left unchecked, the load runs away and `apport` runs to try to gather a crash dump.
