Re: [orientdb] Re: Today, our OrientDB crashed without any errors.

Hi, OK let's look at /var/log/messages then. If your application is exited without your intention OS has to log it somewhere . So let's keep digging. Also what about DB server logs . Could you send them to us ? вс, 10 Апр 2016, 8:54 Erik Pragt : > It used to run on the

Re: [orientdb] Re: Today, our OrientDB crashed without any errors.

It used to run on the same server indeed, but it's not used, so I uninstalled it. On Sun, Apr 10, 2016 at 3:21 PM, 'scott molinari' via OrientDB < orient-database@googlegroups.com> wrote: > Is MySql also running on the same server? Just wondering. > > Scott > > -- > > --- > You received this

Re: [orientdb] Re: Today, our OrientDB crashed without any errors.

Is MySql also running on the same server? Just wondering. Scott -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [orientdb] Re: Today, our OrientDB crashed without any errors.

Thanks Andrey. I checked both files, and there's nothing of internet. This is my complete kern.log file for example: Apr 8 10:10:04 localhost kernel: [1282413.300235] audit_printk_skb: 24 callbacks suppressed Apr 8 10:10:04 localhost kernel: [1282413.300241] type=1400 audit(1460103004.823:19):

Re: [orientdb] Re: Today, our OrientDB crashed without any errors.

Hi Erik, Could you inspect following files /var/log/syslog and /var/log/kern.log using grep for example grep -i orient /var/log/kern.log and send us results. On Sat, Apr 9, 2016 at 1:35 AM Erik Pragt wrote: > Thanks! I'm using Ubuntu, I think 14.x > > On 09 Apr 2016, at

Re: [orientdb] Re: Today, our OrientDB crashed without any errors.

Thanks! I'm using Ubuntu, I think 14.x > On 09 Apr 2016, at 00:55, Andrey Lomakin wrote: > > Hi Erik, > If system error happens (that is the only reason which we can think why it > was shutted down without any exceptions) your OS log should contain > information

Re: [orientdb] Re: Today, our OrientDB crashed without any errors.

Hi Erik, If system error happens (that is the only reason which we can think why it was shutted down without any exceptions) your OS log should contain information about that error. Which OS do you use ? On Fri, Apr 8, 2016 at 3:48 PM Erik Pragt wrote: > Hi Luca, > > I'm

Re: [orientdb] Re: Today, our OrientDB crashed without any errors.

Hi Luca, I'm sorry, that was an error on my part: I changed that after the crash, before the crash it was on a very low setting, around 400. I'll change it back anyway! Erik > On 08 Apr 2016, at 20:10, Luca Garulli wrote: > > Hi Erik, > Do you have 2GB of RAM on that

Re: [orientdb] Re: Today, our OrientDB crashed without any errors.

Hi Erik, Do you have 2GB of RAM on that server? if this is the case, you cannot have 8GB of RAM for the Diskcache: -Dstorage.diskCache.bufferSize=8192 So this must be the reason. This is the formula: diskcache + heap < available ram So with 1,5GB of free RAM, try these settings:

Re: [orientdb] Re: Today, our OrientDB crashed without any errors.

Hi Luca, Thanks for your response. - I'm running on Digital Ocean, 2 core 2 gig version. - Around 1500 mb. - What kind of swap do you mean? On an OS level? Thanks for the help! Erik On Friday, April 8, 2016 at 5:39:06 PM UTC+10, l.garulli wrote: > > Hi Erik, > > If OrientDB dies with no log,

Re: [orientdb] Re: Today, our OrientDB crashed without any errors.

Hi Erik, If OrientDB dies with no log, it means the OS killed it. The most common reason is the out of memory. Look at: http://stackoverflow.com/questions/726690/who-killed-my-process-and-why A few questions for you: - How much physical RAM do you have on that server and - How much is

Re: [orientdb] Re: Today, our OrientDB crashed without any errors.

Hi Erik, It's hard to give you an answer here, this is the first report we have from a system that crashes without emitting any logs at all. In other cases, when we had an unexpected crash with few information, it was because of some OS related procedures (eg. process kill under heavy load), but

[orientdb] Re: Today, our OrientDB crashed without any errors.

Btw, running OrientDB 2.1.9. On Friday, April 8, 2016 at 10:05:33 AM UTC+10, Erik Pragt wrote: > > Hi all, > > As the question title suggests, our OrientDB database crashed today. We > got notified by our monitoring server that our sites aren't accepting any > requests anymore, which was