[rabbitmq-discuss] plugin out of date message after upgrade
jerryk at vmware.com
Thu Dec 9 17:50:58 GMT 2010
Hi, again, Steven...
My apologies. I just directed you to a bugzilla report that you can't access. Here's a public mailing list thread from an earlier discovery of this particular problem:
My mis-post notwithstanding, we have a bug filed to try and improve this behavior on Windows. I expect I'll get to it in the relatively near future. In the meantime, you should be good to go without worries.
On Dec 9, 2010, at 9:40 AM, Jerry Kuch wrote:
> Hi, Steven...
> Because these files are all regular parts of Rabbit itself, the likely cause is that the 'src' files in your Rabbit distribution have newer datestamps than the 'beam' Erlang compiled object files.
> You could just 'touch' the '.beam' files in ebin about which you're getting warnings. That will get rid of the alarming noises at startup. Incidentally, if you were getting complaints about plugins being out of date, you may actually have plugins that need updating, but that's not the case here.
> Matthias tells me we have a bug open on the root cause of this:
> In short, the unzipping of the distribution creates files with dates that reflect when and in which order they're extracted from the zip file. If the end result is src files that are younger than their corresponding beam targets, the broker warns you at startup, with Erlang thinking you might be running out of date object code.
> On Dec 9, 2010, at 5:17 AM, Steven Taylor wrote:
>> Is this bad? The broker seems to be running as per normal.
>> I just upgraded to Rabbit 2.2.0, Erlang 5.8.2 (R14B01) and now during startup I get a bunch of messages like this:
>> *WARNING* rabbit: Object code (delegate) out of date
>> *WARNING* rabbit: Object code (delegate_sup) out of date
>> *WARNING* rabbit: Object code (file_handle_cache) out of date
>> *WARNING* rabbit: Object code (gatherer) out of date
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss