diff --git a/content/2016-09.md b/content/2016-09.md
index f78abafdf..8f218d1c6 100644
--- a/content/2016-09.md
+++ b/content/2016-09.md
@@ -174,3 +174,12 @@ $ rm -rf ~/ciat-gender-2016-09-06/SimpleArchiveFormat/
- Reading about PostgreSQL maintenance and it seems manual vacuuming is only for certain workloads, such as heavy update/write loads
- I suggest we disable our nightly manual vacuum task, as we're a mostly read workload, and I'd rather stick as close to the documentation as possible since we haven't done any testing/observation of PostgreSQL
- See: https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html
+- CGSpace went down and the error seems to be the same as always (lately):
+
+```
+2016-09-07 11:39:23,162 ERROR org.dspace.storage.rdbms.DatabaseManager @ SQL connection Error -
+org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
+...
+```
+
+- Since CGSpace had crashed I quickly deployed the new LDAP settings before restarting Tomcat
diff --git a/public/2016-09/index.html b/public/2016-09/index.html
index 7e4625ca1..8aeb4ad6f 100644
--- a/public/2016-09/index.html
+++ b/public/2016-09/index.html
@@ -278,6 +278,16 @@ $ rm -rf ~/ciat-gender-2016-09-06/SimpleArchiveFormat/
Reading about PostgreSQL maintenance and it seems manual vacuuming is only for certain workloads, such as heavy update/write loads
I suggest we disable our nightly manual vacuum task, as we’re a mostly read workload, and I’d rather stick as close to the documentation as possible since we haven’t done any testing/observation of PostgreSQL
See: https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html
+CGSpace went down and the error seems to be the same as always (lately):
+
+
+2016-09-07 11:39:23,162 ERROR org.dspace.storage.rdbms.DatabaseManager @ SQL connection Error -
+org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
+...
+
+
+
+- Since CGSpace had crashed I quickly deployed the new LDAP settings before restarting Tomcat
diff --git a/public/index.xml b/public/index.xml
index 2e71eda95..26ef2531b 100644
--- a/public/index.xml
+++ b/public/index.xml
@@ -216,6 +216,16 @@ $ rm -rf ~/ciat-gender-2016-09-06/SimpleArchiveFormat/
<li>Reading about PostgreSQL maintenance and it seems manual vacuuming is only for certain workloads, such as heavy update/write loads</li>
<li>I suggest we disable our nightly manual vacuum task, as we’re a mostly read workload, and I’d rather stick as close to the documentation as possible since we haven’t done any testing/observation of PostgreSQL</li>
<li>See: <a href="https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html">https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html</a></li>
+<li>CGSpace went down and the error seems to be the same as always (lately):</li>
+</ul>
+
+<pre><code>2016-09-07 11:39:23,162 ERROR org.dspace.storage.rdbms.DatabaseManager @ SQL connection Error -
+org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
+...
+</code></pre>
+
+<ul>
+<li>Since CGSpace had crashed I quickly deployed the new LDAP settings before restarting Tomcat</li>
</ul>
diff --git a/public/tags/notes/index.xml b/public/tags/notes/index.xml
index 036d668d7..987926210 100644
--- a/public/tags/notes/index.xml
+++ b/public/tags/notes/index.xml
@@ -216,6 +216,16 @@ $ rm -rf ~/ciat-gender-2016-09-06/SimpleArchiveFormat/
<li>Reading about PostgreSQL maintenance and it seems manual vacuuming is only for certain workloads, such as heavy update/write loads</li>
<li>I suggest we disable our nightly manual vacuum task, as we’re a mostly read workload, and I’d rather stick as close to the documentation as possible since we haven’t done any testing/observation of PostgreSQL</li>
<li>See: <a href="https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html">https://www.postgresql.org/docs/9.3/static/routine-vacuuming.html</a></li>
+<li>CGSpace went down and the error seems to be the same as always (lately):</li>
+</ul>
+
+<pre><code>2016-09-07 11:39:23,162 ERROR org.dspace.storage.rdbms.DatabaseManager @ SQL connection Error -
+org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool error Timeout waiting for idle object
+...
+</code></pre>
+
+<ul>
+<li>Since CGSpace had crashed I quickly deployed the new LDAP settings before restarting Tomcat</li>
</ul>