Hi,
I found the tool "resize" in /usr/lib/x86_64-linux-gnu/qpid/msgstore/resize.
I used resize like this:
/usr/lib/x86_64-linux-gnu/qpid/msgstore/resize --num-jfiles=16
--jfile-size-pgs=48 /var/spool/qpidd/rhm/jrnl/000b/<QUEUE-NAME>
Now is fine!
Thanks!
--
Thiago Henrique
www.adminlinux.com.br
On 10-10-2012 08:45, 3.listas@adminlinux.com.br wrote:
> Hi,
>
> Thanks for the explanation Pavel.
> I'm already using 8 journal files.
> I can`t find the `resize` tool. Does anyone know if there is package
> for ubuntu ?
> Thank you all
>
> --
> Thiago Henrique
> adminlinux.com.br
>
> On 09-10-2012 04:41, Pavel Moravec wrote:
>> Hi,
>> you reached journal limit (reaching approx. 80% of the journal
>> capacity), I assume due to number of journal files less than 8 - see
>> http://qpid.2158936.n2.nabble.com/Message-store-library-from-qpidcomponents-org-generates-JERR-JCNTL-RECOVERJFULL-error-during-recovery-td7345136.html
>> for detailed description.
>>
>> I recommend resizing the journal before starting the qpid broker, see
>> e.g.
>> https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_MRG/2/html/Messaging_Installation_and_Configuration_Guide/Resize_the_Journal.html
>> for reference.
>>
>> To prevent repeating the same problem in future, I recommend either
>> increase journal files to at least 8 if relevant (or wait for the fix
>> to be included either in 0.18 or 0.20, not sure now), or if you
>> really reached the journal capacity by many enqueues, read
>> https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_MRG/2/html/Messaging_Installation_and_Configuration_Guide/sect-Determining_Journal_Size.html
>> to properly determine your journal size.
>>
>> Kind regards,
>> Pavel Moravec
>>
>>
>> ----- Original Message -----
>>> From: "3.listas@adminlinux.com.br" <listas@adminlinux.com.br>
>>> To: users@qpid.apache.org
>>> Sent: Monday, October 8, 2012 8:22:16 PM
>>> Subject: Cannot start qpidd
>>>
>>> Hi,
>>>
>>> I have a "ubuntu12.04 + qpidd-0.14-2 + qpidd-msgstore-0.14-1"
>>> cluster.
>>> My cluster was working perfectly. I turned it off without problems.
>>> But now the command "service qpidd start" does not turn on the
>>> daemon.
>>> The only problem seems to be in a queue:
>>>
>>> Oct 8 17:32:14 net17 qpidd[12316]: 2012-10-08 17:32:14 critical
>>> Unexpected error: Queue thiago.test: recoverQueues() failed:
>>> jexception
>>> 0x0205 jcntl::recover() threw JERR_JCNTL_RECOVERJFULL: Journal data
>>> files full, cannot write. (MessageStoreImpl.cpp:826)
>>>
>>> I need to start the cluster and I can't lose the messages of the
>>> other
>>> queues.
>>> Is there a way to make qpidd daemon to ignore this problem with the
>>> queue thiago.test?
>>> Is there a way to make qpidd to ignore the thiago.test queue and
>>> start
>>> the cluster?
>>>
>>> Thanks.
>>>
>>> --
>>> Thiago Henrique
>>> adminlinux.com.br
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
|