Path: csiph.com!usenet.pasdenom.info!nntpfeed.proxad.net!proxad.net!feeder1-1.proxad.net!217.73.144.45.MISMATCH!feeder2.ecngs.de!ecngs!feeder.ecngs.de!81.171.118.61.MISMATCH!peer01.fr7!news.highwinds-media.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Tim Watts <tw_usenet@dionic.net>
Newsgroups: comp.os.linux.misc
Subject: Re: CentOS 7.1 VPS wont respong after a reboot
Date: Sat, 09 May 2015 09:36:45 +0100
Lines: 18
Message-ID: <tht02c-cs5.ln1@squidward.dionic.net>
References: <3f9f2f9e-257c-47c5-acd8-63a71f877d84@googlegroups.com> <2af9b42a-e466-4eac-96b1-0a3750cd758e@googlegroups.com> <uq1u1c-l4k.ln1@squidward.dionic.net> <d2c760f0-10d6-42a9-805e-d346b52eadc0@googlegroups.com> <sd8u1c-bim.ln1@squidward.dionic.net> <68faa2ca-45ae-474f-ad95-92988af8f711@googlegroups.com> <vrqu1c-473.ln1@squidward.dionic.net> <55e798ee-d8d7-47d2-801c-b20f9cbb559e@googlegroups.com> <49su1c-bb4.ln1@squidward.dionic.net> <de526c58-c9d5-482d-bbe5-c48c0a3c4725@googlegroups.com> <kguu1c-p37.ln1@squidward.dionic.net> <87beea53-140c-4c4e-8a39-814c7b828672@googlegroups.com> <4l1v1c-h0a.ln1@squidward.dionic.net> <02a9f481-ebfe-44c5-afff-54754c32bb58@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-7; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net SUHMiCEe5A94NwQbxhUkNgyHfzQCLLVfNwORX8zMopcnVCsDs0
X-Orig-Path: squidward.dionic.net!not-for-mail
Cancel-Lock: sha1:GLUL4PTKlvB/sYiT9+zBrp5zKKc=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
In-Reply-To: <02a9f481-ebfe-44c5-afff-54754c32bb58@googlegroups.com>
X-Received-Bytes: 2187
X-Received-Body-CRC: 3276251168
Xref: csiph.com comp.os.linux.misc:14746

On 09/05/15 05:13, Φώντας Λαδοπρακόπουλος wrote:

> I have no idea what to look for as iam new to this VPS stuff :)
>

Well, just start looking then - it's what the rest of us had to do. No 
point in sitting here putting it off.

People are happy to help, but you have to get in there and look at 
stuff. And really look. I've told you all I can - now prepare for the 
boredom of scanning through pages of log files wondering if anything 
might be relevant.


Or you could just ignore it and hope it does not happen again - a valid 
strategy for one offs - I do it occasionally where a non critical system 
has had no previous history of problems and it does not seem to be a 
repeating event.