Issue #3650 has been updated by Alan Barrett.
sqlite doesn't allow multiple simultaneous writers, true. But it does allow multiple simultaneous clients, provided no more than one client is inside a write transaction at any time. If you keep the database locked for as short a time as possible, it should be fine. See http://www.sqlite.org/faq.html#q5 . ---------------------------------------- Bug #3650: more than one simultaneous client fails with sqlite storedconfigs http://projects.puppetlabs.com/issues/3650 Author: Alan Barrett Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Affected version: 0.25.4 Keywords: Branch: On a puppetmaster configured to use sqlite for storeconfigs, no more than one simultaneous client conneciton seems to work. /etc/puppet/puppet.conf contains these lines: <pre> [puppetmasterd] storeconfigs = true dbadapter = sqlite3 dblocation = /var/puppet/db/storeconfigs.sqlite </pre> The following command is executed simultaneously on two clients: <pre> /usr/local/sbin/puppetd --onetime --test --noop </pre> On one client, it works. On the other client, it hangs for some time, then reports this error: <pre> err: Could not retrieve catalog from remote server: end of file reached warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run </pre> Changing to storeconfigs = false in the puppet.conf file allows both clients to work simultaneously. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- 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.
