https://redmine.gc.cuny.edu/https://redmine.gc.cuny.edu/favicon.ico2017-03-07T12:07:18ZCUNY Graduate Center - Project Tracking SystemCUNY Academic Commons - Bug #7762: RBE post didn't go throughhttps://redmine.gc.cuny.edu/issues/7762?journal_id=309652017-03-07T12:07:18ZLuke Waltzerlwaltzer@gc.cuny.edu
<ul></ul><p>(the reply that's there I posted directly)</p> CUNY Academic Commons - Bug #7762: RBE post didn't go throughhttps://redmine.gc.cuny.edu/issues/7762?journal_id=309672017-03-07T15:05:50ZLuke Waltzerlwaltzer@gc.cuny.edu
<ul><li><strong>File</strong> <a href="/attachments/5245">Screen Shot 2017-03-07 at 10.03.18 AM.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/5245/Screen%20Shot%202017-03-07%20at%2010.03.18%20AM.png">Screen Shot 2017-03-07 at 10.03.18 AM.png</a> added</li><li><strong>Priority name</strong> changed from <i>Normal</i> to <i>Urgent</i></li></ul><p>Elevating priority... confirmed RBE is not working on another thread -- <a class="external" href="https://commons.gc.cuny.edu/groups/coursetest/forum/topic/testing-rbe/#post-53858">https://commons.gc.cuny.edu/groups/coursetest/forum/topic/testing-rbe/#post-53858</a>.</p>
<p>Screenshot of email attached.</p> CUNY Academic Commons - Bug #7762: RBE post didn't go throughhttps://redmine.gc.cuny.edu/issues/7762?journal_id=309682017-03-07T15:09:55ZLuke Waltzerlwaltzer@gc.cuny.edu
<ul></ul><p>Just got four emails from this post -- <a class="external" href="https://commons.gc.cuny.edu/groups/digital-humanities-initiative/forum/topic/fwd-invitation-to-digital-paxton-launch-events-2/">https://commons.gc.cuny.edu/groups/digital-humanities-initiative/forum/topic/fwd-invitation-to-digital-paxton-launch-events-2/</a>.</p>
<p>And then just got four rejection messages each for my earlier replies.</p>
<p>Hi there,</p>
<p>Unfortunately, your reply to the forum topic could not be posted because it appears you have already made the same reply.</p>
<p>Here is a copy of your reply:</p>
<p>"RBE."</p>
<p>We apologize for any inconvenience this may have caused.</p> CUNY Academic Commons - Bug #7762: RBE post didn't go throughhttps://redmine.gc.cuny.edu/issues/7762?journal_id=309782017-03-07T17:03:16ZRaymond Hoh
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul><p>It looks like RBE stopped working at 11:10am ET.</p>
<p>Not sure why. Looking into it.</p> CUNY Academic Commons - Bug #7762: RBE post didn't go throughhttps://redmine.gc.cuny.edu/issues/7762?journal_id=309812017-03-07T17:48:26ZRaymond Hoh
<ul></ul><p>So the problem is the remote POST response used to trigger RBE is no longer responding:<br /><a class="external" href="https://github.com/cuny-academic-commons/cac/blob/1.10.x/wp-content/plugins/bp-reply-by-email/includes/bp-rbe-functions.php#L1350">https://github.com/cuny-academic-commons/cac/blob/1.10.x/wp-content/plugins/bp-reply-by-email/includes/bp-rbe-functions.php#L1350</a></p>
<p>I'm guessing IT has put in some security restrictions on POST responses. For the moment, I have manually triggered RBE. I'll look into adding some code that doesn't use a POST response to trigger RBE on the RBE settings page.</p> CUNY Academic Commons - Bug #7762: RBE post didn't go throughhttps://redmine.gc.cuny.edu/issues/7762?journal_id=309822017-03-07T17:54:45ZLuke Waltzerlwaltzer@gc.cuny.edu
<ul></ul><p>Boone, think this is worth a follow up with Lihua?</p> CUNY Academic Commons - Bug #7762: RBE post didn't go throughhttps://redmine.gc.cuny.edu/issues/7762?journal_id=309832017-03-07T17:56:28ZRaymond Hoh
<ul></ul><p>Let me do some more debugging before we contact Lihua.</p> CUNY Academic Commons - Bug #7762: RBE post didn't go throughhttps://redmine.gc.cuny.edu/issues/7762?journal_id=309852017-03-08T00:49:34ZRaymond Hoh
<ul></ul><p>I've <a href="https://github.com/r-a-y/bp-reply-by-email/compare/66dbfdd028...2b541493fa" class="external">written some new logic</a> so RBE can spawn new inbox checks from the RBE admin settings page.</p>
<p>This approach doesn't use a loopback POST response as before, but instead uses AJAX to do the initial ping.</p>
<p>The good thing is this approach will probably stop our problem with RBE duplicate posts from occurring since you can only spawn new inbox checks from the admin settings page and not on a pageload basis like before.</p>
<p>The problem is if the Commons goes down or if RBE isn't able to connect to the inbox during a scheduled ping, someone will need to manually go to the RBE admin settings page and hit the "Connect" button.</p>
<p>To remedy this, I can write a task hooked to WP cron (perhaps run hourly) to check if RBE is connected. If RBE isn't connected, it can email some of us to go to the RBE settings page and re-connect.</p>
<p>FYI: This code is live on the Commons, but I haven't committed it to the CAC repo yet as I'm still monitoring things, but initial logs look good on my end.</p>
<hr />
<p>It might be good to ping Lihua just to see what has changed exactly or to see if something like fail2ban is blocking the loopback POST response.</p> CUNY Academic Commons - Bug #7762: RBE post didn't go throughhttps://redmine.gc.cuny.edu/issues/7762?journal_id=310342017-03-11T11:28:46ZRaymond Hoh
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li><li><strong>Target version</strong> set to <i>1.10.13</i></li></ul><p>Boone - I've added the updated RBE code to 1.10.x branch:<br /><a class="external" href="https://github.com/cuny-academic-commons/cac/commit/14cc98d54675e907dc00726efd2757a8b48e52bb">https://github.com/cuny-academic-commons/cac/commit/14cc98d54675e907dc00726efd2757a8b48e52bb</a></p>
<p>And on production, I have cherry-picked the commit. RBE is already up-and-running; you shouldn't have to do anything for the maintenance release today.</p>
<p>One thing I haven't done is write a task hooked to WP cron to email one of us should the IMAP connection go down, but I can do this before the next maintenance release on the 21st.</p>
<p>Going to mark this as resolved.</p> CUNY Academic Commons - Bug #7762: RBE post didn't go throughhttps://redmine.gc.cuny.edu/issues/7762?journal_id=311442017-03-22T17:32:25ZRaymond Hoh
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-6 priority-5 priority-high4 closed" href="/issues/7825">Bug #7825</a>: WP Cron fails to spawn on production</i> added</li></ul> CUNY Academic Commons - Bug #7762: RBE post didn't go throughhttps://redmine.gc.cuny.edu/issues/7762?journal_id=426532019-03-12T03:31:25ZRaymond Hoh
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/5884">Bug #5884</a>: Reply by email double posting issues</i> added</li></ul> CUNY Academic Commons - Bug #7762: RBE post didn't go throughhttps://redmine.gc.cuny.edu/issues/7762?journal_id=426552019-03-12T03:33:52ZRaymond Hoh
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-7 priority-4 priority-default" href="/issues/8991">Bug #8991</a>: RBE duplicate email message issue</i> added</li></ul> CUNY Academic Commons - Bug #7762: RBE post didn't go throughhttps://redmine.gc.cuny.edu/issues/7762?journal_id=426572019-03-12T03:34:22ZRaymond Hoh
<ul><li><strong>Related to</strong> deleted (<i><a class="issue tracker-1 status-7 priority-4 priority-default" href="/issues/8991">Bug #8991</a>: RBE duplicate email message issue</i>)</li></ul>