<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>Barry,</div><div><br data-mce-bogus="1"></div><div>That was my article and I don't remember the circumstances now and had completely forgot that I had written this up. Zimbra support and Rich King made the recommendation but root cause was unknown. The server was SSD's in a raid configuration and was on a KVM platform that I use for myself, wife and kids. Once the general recommendation failed, we went to last resort which is not a very good solution since you are deleting/importing. I had a single bob instance.<br></div><div><br data-mce-bogus="1"></div><div>I will add the following for possible root cause - we believed it was tied to composing and sending via the web interface. My wife maintained that odd things were happening with her various browsers and plugin's on her mac and she was getting strange errors from time to time when composing messages. I should have paid more attention :-) but her use of noscript and various other security plugin's seemed root cause to me at the time and I failed to investigate this further. This would be a 8.7+ NETWORK release. <br></div><div><br data-mce-bogus="1"></div><div>Good Luck<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><div>Jim<br data-mce-bogus="1"></div><div><br></div><span id="zwchr" data-marker="__DIVIDER__">----- On Jul 30, 2019, at 10:10 AM, Barry de Graaff <info@barrydegraaff.tk> wrote:<br></span><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div style="font-family:'arial' , 'helvetica' , sans-serif;font-size:12pt;color:#000000"><div>I will discuss it on the call tonight.</div><br><div>But my understanding of that article is, copy the blobs (that are in my case msg files/eml format).</div><div>Toss em in a tgz per account and re-import then per account.</div><br><div>Then delete original msg files that generated the error.</div><br><div>But there must be an easier way.... but I dunno what that is. Anyway the cause here was a storage</div><div>network failure. So it is not really Zimbra's fault.</div><br><div>Kind regards, <br><br>Barry de Graaff<br>Zeta Alliance <br>Co-founder & Developer<br>zetalliance.org | github.com/Zimbra-Community<br><br>Signal: +31 617 220 227<br>Fingerprint: 97f4694a1d9aedad012533db725ddd156d36a2d0</div><br><hr id="zwchr"><div><b>From: </b>"Noah Price" <noah-zeta@prxy.com><br><b>To: </b>"users" <users@lists.zetalliance.org><br><b>Sent: </b>Tuesday, 30 July, 2019 19:02:25<br><b>Subject: </b>Re: [Users] How to recover from WARN Unexpected blob found<br></div><br><div><div style="font-family:'times new roman' , 'new york' , 'times' , serif;font-size:12pt;color:#000000"><div style="font-family:'times new roman' , 'new york' , 'times' , serif;font-size:12pt;color:#000000"><div>Hi Barry,</div><br><div>Isn't that article ultimately just saying delete the blob data?<br></div><br><div>Seems like that is what Zimbra recommends<br></div><div><a href="https://wiki.zimbra.com/wiki/Zimbra_Suite_Plus/Zimbra_HSM_Plus/Checking_the_message_BLOBs_health" rel="nofollow%20noopener%20noreferrer nofollow noopener noreferrer" target="_blank">https://wiki.zimbra.com/wiki/Zimbra_Suite_Plus/Zimbra_HSM_Plus/Checking_the_message_BLOBs_health</a><br></div><div><em>"Unexpected BLOB" errors are commonly caused by a problem in the deletion process of an item.</em><br></div></div><div style="font-family:'times new roman' , 'new york' , 'times' , serif;font-size:12pt;color:#000000"><br></div><div style="font-family:'times new roman' , 'new york' , 'times' , serif;font-size:12pt;color:#000000">I'm interested since I've also done some recent blob checks finding unexpected blobs, but assumed they were from messages deleted by the user at some point so the blob data could just be removed.<br></div><div style="font-family:'times new roman' , 'new york' , 'times' , serif;font-size:12pt;color:#000000"><br></div><div style="font-family:'times new roman' , 'new york' , 'times' , serif;font-size:12pt;color:#000000">Noah<br></div><div style="font-family:'times new roman' , 'new york' , 'times' , serif;font-size:12pt;color:#000000"><br></div><div style="font-family:'times new roman' , 'new york' , 'times' , serif;font-size:12pt;color:#000000"><br></div><div style="font-family:'times new roman' , 'new york' , 'times' , serif;font-size:12pt;color:#000000"><hr id="zwchr"><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:'helvetica' , 'arial' , sans-serif;font-size:12pt"><b>From: </b>"Barry de Graaff" <info@barrydegraaff.tk><br><b>To: </b>"users" <users@lists.zetalliance.org><br><b>Sent: </b>Tuesday, July 30, 2019 12:44:58 AM<br><b>Subject: </b>Re: [Users] How to recover from WARN Unexpected blob found<br></blockquote></div><div><blockquote style="border-left:2px solid #1010ff;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:'helvetica' , 'arial' , sans-serif;font-size:12pt">Seems we need to do something like so:<br>https://silentadmin.gsans.com/my-toolbox/zimbra-admin/zmblobchk-and-unexpected-blob-error-messages/<br><br>Kind regards, <br><br>Barry de Graaff<br>Zeta Alliance <br>Co-founder & Developer<br>zetalliance.org | github.com/Zimbra-Community<br><br>Signal: +31 617 220 227<br>Fingerprint: 97f4694a1d9aedad012533db725ddd156d36a2d0<br><br>----- Original Message -----<br>From: "info" <info@zetalliance.org><br>To: users@lists.zetalliance.org<br>Sent: Tuesday, 30 July, 2019 09:24:29<br>Subject: How to recover from WARN Unexpected blob found<br><br>Hello All,<br><br>I have run the command:<br><br>zxsuite powerstore doCheckBlobs start<br><br>It return some 200 warning like:<br> WARN Unexpected blob found<br><br>How do I fix that? I also tried to run `zmblobchk start` but that throws an error:<br>(even on a clean server)<br><br>[] INFO: Setting mysql connector property: maxActive=100<br>[] INFO: Setting mysql connector property: maxActive=100<br>Checking mailbox 1.<br>invalid request: org.openzal.zal.extension.InternalOverrideStoreManager is not supported<br><br><br>The zmdbintergrityreport does not show any error.<br><br>Thanks,<br><br>Barry</blockquote></div></div></div></div></div><br></blockquote></div></div></body></html>