X-Git-Url: https://review.fuel-infra.org/gitweb?a=blobdiff_plain;ds=sidebyside;f=website%2Fmessages%2FPLMC9.md;fp=website%2Fmessages%2FPLMC9.md;h=f0183b8af7b56af98c9d156e5e56571d97b2e73d;hb=b87d2f4e68281062df1913440ca5753ae63314a9;hp=0000000000000000000000000000000000000000;hpb=ab0ea530b8ac956091f17b104ab2311336cfc250;p=packages%2Fprecise%2Fmcollective.git

diff --git a/website/messages/PLMC9.md b/website/messages/PLMC9.md
new file mode 100644
index 0000000..f0183b8
--- /dev/null
+++ b/website/messages/PLMC9.md
@@ -0,0 +1,24 @@
+---
+layout: default
+title: Message detail for PLMC9
+toc: false
+---
+
+Detail for Marionette Collective message PLMC9
+===========================================
+
+Example Message
+---------------
+
+    Expired Message: message 8b4fe522f0d0541dabe83ec10b7fa446 from cert=client@node created at 1358840888 is 653 seconds old, TTL is 60
+
+Additional Information
+----------------------
+
+Requests sent from clients to servers all have a creation time and a maximum validity time called a TTL.
+
+This message indicates that a message was received from the network but that it was determined to be too based on the TTL settings.
+
+Usually this happens because your clocks are not in sync - something that can be fixed by rolling out a tool like ntp across your server estate.
+
+It might also happen during very slow network conditions or when the TTL is set too low for your general network latency.