Bug #4632

async_storedconfigs not exporting resources after days of waiting

Added by Joe McDonagh over 1 year ago. Updated 3 months ago.

Status:Needs More Information Start date:08/26/2010
Priority:Normal Due date:
Assignee:Joe McDonagh % Done:

0%

Category:stored configuration
Target version:-
Affected Puppet version:0.25.4 Branch:
Keywords:storedconfigs async_storedconfigs
Votes: 0

Description

I built a node days ago, and the exported resources still aren’t there in the resources table. I disabled async_storedconfigs, the resources are exported and collected.

mysql> select * from resources where exported = 1 and title = "@@check_procs_on_smtp003.somesite.com";
+-------+-----------------------------------------+----------------+---------+----------------+----------+------+---------------------+---------------------+
| id    | title                                   | restype        | host_id | source_file_id | exported | line | updated_at          | created_at          |
+-------+-----------------------------------------+----------------+---------+----------------+----------+------+---------------------+---------------------+
| 16251 | @@check_procs_on_somesite.com           | Nagios_service |      32 |            113 |        1 |  179 | 2010-06-16 13:16:35 | 2010-05-17 23:58:31 |
+-------+-----------------------------------------+----------------+---------+----------------+----------+------+---------------------+---------------------+
1 row in set (0.00 sec)

mysql> select * from resources where exported = 1 and title = "@@check_procs_on_somecompany.somesite.com";
Empty set (0.00 sec)

mysql> select * from resources where exported = 1 and title like  "%somecompany%";
Empty set (0.00 sec)

After disabling async:

+-------+-------------------------------------------------------------------------------------------+--------------------------+---------+----------------+----------+------+---------------------+---------------------+
| id    | title                                                                                     | restype                  | host_id | source_file_id | exported | line | updated_at          | created_at          |
+-------+-------------------------------------------------------------------------------------------+--------------------------+---------+----------------+----------+------+---------------------+---------------------+
...stuff...tonsofit

I still have one master in a broken state with async still on for troubleshooting purposes. I’m not really sure what the best info to give you guys would be here. This is using stomp as the queue.


Related issues

related to Puppet - Bug #4694: Storeconfig issue with AR/MySQL Duplicate 09/02/2010

History

Updated by Rein Henrichs over 1 year ago

  • Status changed from Unreviewed to Investigating
  • Assignee set to Rein Henrichs

Updated by James Turnbull 12 months ago

  • Status changed from Investigating to Needs More Information
  • Assignee changed from Rein Henrichs to Joe McDonagh

Joe is this still an issue?

Updated by Joe McDonagh 12 months ago

Unfortunately, yes. However, we are still on .25.4 and will not be upgrading til 2.6.5 is released. To add to this misfortune, I am leaving Rapid7 for a new company come Friday. I may be contracted to do the 2.6.5 migration, but I am not sure yet. I’d like to keep this ticket open until I can figure if it still affects 2.6.5 + stomp.

Updated by James Turnbull 3 months ago

  • Category set to stored configuration

Also available in: Atom PDF