1 bitoin for the one who can help me fix my server issue

[fffeee]

Hi,

I have a huge problem with my bitcoind bitcoin server. It always crashes (about 2times a day) and I cant figure out what is wrong.. I`m not that into server administration, so I`m not able to fix this by myself. It runs on ubuntu lucid platform.
I would appreciate your help.

Thanks in advance.

[1680187566]

1680187566

[1680187566]

1680187566

[Matthew N. Wright]

Hi,

I have a huge problem with my bitcoind bitcoin server. It always crashes (about 2times a day) and I cant figure out what is wrong.. I`m not that into server administration, so I`m not able to fix this by myself. It runs on ubuntu lucid platform.
I would appreciate your help.

Thanks in advance.

Buy more memory for your VPS.

[fffeee]

Could that really be the problem?

[Matthew N. Wright]

Could that really be the problem?

In my experiences, things that crash without explanation after functioning completely normally do so because of a lack of memory.

[fffeee]

ok thanks.. I`ll try to buy more memory..

[thantomaniac]

If the server is shutting down without any warning or errors, check your temps.

[dooglus]

Hi,

I have a huge problem with my bitcoind bitcoin server. It always crashes (about 2times a day) and I cant figure out what is wrong.. I`m not that into server administration, so I`m not able to fix this by myself. It runs on ubuntu lucid platform.
I would appreciate your help.

Thanks in advance.

Do you manage the server yourself, or do you rent it from a company?

I had a problem with bitcoind shutting down most days, and it turned out the shared hosting provider it was running on were doing some kind of backup most nights, which involved sending a signal to all running processes, which killed the bitcoind.

It took dozens of emails back and forth before the hosting provider would even acknowledge that they were sending signals to all running processes - the support staff you get to talk to aren't always particularly knowledgeable.

[Dansko]

Hello,

After a crash reboot the server and look at /var/log/messages. This should give you a clear sign of what is going on. Is this a new issue or have you always had this problem? If its new it suggests it was caused by an update.