PLUMPUDDING wrote:I couldn't get on again yesterday morning but it had come back last night with all the avatars.
Could you let us know what caused it and should we be worrying about viruses affecting our computers?
Yes you should always worry about malware (AKA viruses), always ensure your anti-malware software is up to date, delete suspicious e-mails without opening them and never follow links sent in e-mails unless they are ones you specifically requested, never accept requests for people to take over your computer to fix something, never ever believe any incoming calls from any IT support people.
IT Support, you call them on the number you know to be correct and if they need to connect you control it.
Suspicious = anything unsolicited, anything making offers to change your life, anything where they do not put your correct name in it, anything with English she is worded unusual, anything.... you get the picture.
As for what went wrong, the website got a bit b*****ed.
Oh and by the way, KG is a small forum on the server supporting all of Mortens magazines forums.
==============================================================================================================
29/09/2016 21:34
It seems a corrupt database table stopped the Database server from running according to 1&1 support, which stopped the plesk services from starting. Fixed MySQL, and server seems OK now.
1&1 were very helpful in helping me access the server, and they looked at the logs and identified the problem... then they left me to it!
Phew!!!
Wayne
29/09/2016 :22:17
I don’t think it was MySQL perse, although it didn’t start due to a service call Polkit not being able to start. Basically, after tracking that down (after following 1&1 red herring of corrupt DB table [they were OK actually in the end]) I re-installed Polkit: rpm reinstall polkit, and was then able to start MySQL.
Previous to that, I had instructed Plesk to restore all permissions on Web domains to their default, which I think was responsible for KG Forum not working until I manually fixed the permissions later, as it is a sub-domain.
All seems OK now.
Wayne
04/10/2016 08:37
Hi Peter, it hopefully should be working now. Thanks for spotting it. You were correct in that it was a permissions problem left over from last week.
Sorry it took me a few days to sort it; I should have spotted it straight away, but it’s been a bit hectic.
Regards, Wayne
==============================================================================================================