-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yes, I was focusing on the crashing on null context here. The large memory required will be worked on too.
Best regards, Matthijs On 06/21/2012 07:02 PM, Paul Wouters wrote: > On Thu, 21 Jun 2012, Matthijs Mekking wrote: > >> I have now implemented I think a reasonable strategy in trunk, >> r6450. If this happens, the signer will fail the sign task, back >> off the task and reload the engine. This will stop workers and >> drudgers, reopen the connection to the HSM and start workers and >> drudgers again. The next time, the backed off task runs (or >> another task that is scheduled earlier), the drudgers try to >> create a new context and do the sign jobs. >> >> Let me know if you are satisfied with this approach. > > If it avoids the crash I'm happy, though it still does not resolve > our issue of the large amounts of RAM needed, but since that was > happening for us on a test deployment without optout (and with less > RAM) we won't be hitting this issue again, though other people > might. > > Paul -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJP44ogAAoJEA8yVCPsQCW5peoH/RPpPvRYYXoo1l4NafpO0aGk eNfWAMFhxeZIp2j9kiWNYhcwiSYjeAmlLRAZOa7qlGb62hDtVKd+KkLSjXef167G X/euk2N824vW1g4Pr3BP2Kpk7v2fpJpkkYIxTz67xaiXOUF+HWlsnzruYBt1rf8J NB7kP7MPHU3hLaZ3IUbaO/WvPF4zRwEm2Yi0woglxxyl6oueWnLYctlhRComS5on uglr1/0/VTG1+AGAf7mlbE55gttT3irD9q3Deaolvq0Wn2cqgZmghC687RGDVZrC YQcriodBVUn1Vh7nGWcrmWVSQlBxM7bLw3ua60jlLD0vxRpNVXzHnlIYf85+tGk= =gjyg -----END PGP SIGNATURE----- _______________________________________________ Opendnssec-user mailing list [email protected] https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
