Ivaylo,

We will need to await help from others.  This is not a crash scenario that I 
happen to know.  The other problem is that today and tomorrow are holidays in 
the U.S.

The typical requests at this point are for a copy of your app.config and any 
information from the Riak crash.log that details the crash point.  That might 
lead someone to giving you a solid answer.

Matthew


On Nov 27, 2014, at 10:46 AM, Ivaylo Panitchkov <[email protected]> 
wrote:

> 
> Hi Matthew,
> 
> That happened few times in the past with different versions.
> The one we are running right now is 1.4.7 with bitcask and the problem 
> occurred again few days ago.
> 
> Thanks,
> Ivaylo
> 
> 
> 
> On Thu, Nov 27, 2014 at 10:37 AM, Matthew Von-Maszewski <[email protected]> 
> wrote:
> What version of Riak?  What backend are you using (bitcask, memory, leveldb)?
> 
> Matthew
> 
> On Nov 27, 2014, at 10:30 AM, Ivaylo Panitchkov <[email protected]> 
> wrote:
> 
>> 
>> Hi Alexander,
>> 
>> Yes, they are set properly in /etc/security/limits.conf 
>> 
>> Ivaylo
>> 
>> 
>> On Thu, Nov 27, 2014 at 9:44 AM, Alexander Sicular <[email protected]> 
>> wrote:
>> Are you sure your ulimit persists through reboot?
>> 
>> -Alexander
>> 
>> @siculars
>> http://siculars.posthaven.com
>> 
>> Sent from my iRotaryPhone
>> 
>> > On Nov 27, 2014, at 09:39, Ivaylo Panitchkov <[email protected]> 
>> > wrote:
>> >
>> >
>> > Hello,
>> >
>> > I'm running a single Riak server used for dev purposes and noticed 
>> > something unexpected.
>> > It happened few times in the past and I just want to share my observation 
>> > with you if someone experienced the same problem.
>> > While the server was up and running it happened the machine needed to be 
>> > rebooted.
>> > Once the reboot cycle completed I noticed the running Riak process 
>> > suddenly crashed.
>> > If I try to start it again it continues crashing.
>> > I haven't time to investigate what causing the problem but the way to 
>> > solve it was to simply delete the content of the bitcask folder (it's a 
>> > dev server so nothing critical there).
>> >
>> > Thanks in advance,
>> > Ivaylo
>> >
>> >
>> > --
>> > Ivaylo Panitchkov
>> > Software developer
>> > Hibernum Creations Inc.
>> >
>> > Ce courriel est confidentiel et peut aussi être protégé par la loi.Si vous 
>> > avez reçu ce courriel par erreur, veuillez nous en aviser immédiatement en 
>> > y répondant, puis supprimer ce message de votre système. Veuillez ne pas 
>> > le copier, l’utiliser pour quelque raison que ce soit ni divulguer son 
>> > contenu à quiconque.
>> > This email is confidential and may also be legally privileged. If you have 
>> > received this email in error, please notify us immediately by reply email 
>> > and then delete this message from your system. Please do not copy it or 
>> > use it for any purpose or disclose its content.
>> > _______________________________________________
>> > riak-users mailing list
>> > [email protected]
>> > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>> 
>> 
>> 
>> -- 
>> Ivaylo Panitchkov
>> Software developer
>> Hibernum Creations Inc.
>> 
>> Ce courriel est confidentiel et peut aussi être protégé par la loi.Si vous 
>> avez reçu ce courriel par erreur, veuillez nous en aviser immédiatement en y 
>> répondant, puis supprimer ce message de votre système. Veuillez ne pas le 
>> copier, l’utiliser pour quelque raison que ce soit ni divulguer son contenu 
>> à quiconque.
>> This email is confidential and may also be legally privileged. If you have 
>> received this email in error, please notify us immediately by reply email 
>> and then delete this message from your system. Please do not copy it or use 
>> it for any purpose or disclose its content.
>> _______________________________________________
>> riak-users mailing list
>> [email protected]
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
> 
> 
> 
> 
> -- 
> Ivaylo Panitchkov
> Software developer
> Hibernum Creations Inc.
> 
> Ce courriel est confidentiel et peut aussi être protégé par la loi.Si vous 
> avez reçu ce courriel par erreur, veuillez nous en aviser immédiatement en y 
> répondant, puis supprimer ce message de votre système. Veuillez ne pas le 
> copier, l’utiliser pour quelque raison que ce soit ni divulguer son contenu à 
> quiconque.
> This email is confidential and may also be legally privileged. If you have 
> received this email in error, please notify us immediately by reply email and 
> then delete this message from your system. Please do not copy it or use it 
> for any purpose or disclose its content.

_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to