K
Keldyn
Guest
Hello all.
Here is an update on the goings on with neowin.
We had expected to be back online by now ,but a week has passed and sadly this has not come about. Once the new hardware was fitted we thought our problems would be over, however we soon learned this was not the case.
What i will go on to say next may very well be damning for our host but, given their seemingly cold shouldered attitude towards neowin and its staff it is only fair retribution. I dont believe anyone who runs a website should have to depend on such a poorly run hosting company as hosttyme.
Apache was recompiled along with mysql and that didnt quite go to plan. During the process of backing up neowin for transfer over to the "new" server(which we have since learned, is not even our own, but belongs to someone else) they not only wiped all staff email accounts ( they have done this to us 4x) but also managed to wipe all sub-domains, passwords, and permissions were messed up. We can no longer edit, delete, or otherwise replace anything in /public_html/ as they are now somehow protected. I am guessing permissions were screwed during the transfer to the new system. CHMOD does not work on any files. So, not only has hosttyme proven themselves to be an extremely incompetent hosting company, but also, that they have little or any knowledge in the running, the maintainence or even configuration of a server. Neowin could have been back on its feet long before now, had their staff even an inkling of what to do.
If this were not bad enough, hosttyme then had the nerve to turn around and blame our own admin for the demise of the neowin server. Like installing mysql/php ever proved destructive to a server.... They then went on (and the nerve of them!) to ask our own members, without our permission for $5000 to purchase us a new server. (not including rack or bandwidth costs) Hosttyme has further stated, and publically that they no longer want us emergency paging them. Now you tell me. When they have taken to ignoring emails, and filtering those out from neowin, then what else are we supposed to do? The problem is theirs and they refuse to acknowledge it. Bad enough that they refuse or simply dont know how to repair neowin, yet they lay the responsibility on our own shoulders.
Time and time again they have argued that the problem of neowins high server loads were its members, or vbulletin, or mysql or even our graphics fault. All arguments which we have easily dismissed as ludicrous mind you. There are many sites out there running on far less than us and yet exist quite happily. We constantly made cut backs to neowin. We cut features, we trimmed back front page articles from 25 to 15, optimised and tweaked code,removed graphics, cut new registrations, disabled guest access, disabled welcome messages and much more. All of this had little effect. We even made a switch over to ibf board at one stage to prove it was NOT neowins fault. Hosttyme refuse to acknowledge this.
So, as you can now undoubtedly see. With this kind of mentality behind its staff, it is not hard to see why we are having so many problems. As it stands, neowins future right now is and i am sorry to say it, uncertain.
Unless Hosttyme starts taking some responsibility for its actions and begins to show more concern and support for those under its care, then neowin may remain down indefinitely.
Thanks for supporting neowin.net
Keldyn M.
Neowin Staff
Here is an update on the goings on with neowin.
We had expected to be back online by now ,but a week has passed and sadly this has not come about. Once the new hardware was fitted we thought our problems would be over, however we soon learned this was not the case.
What i will go on to say next may very well be damning for our host but, given their seemingly cold shouldered attitude towards neowin and its staff it is only fair retribution. I dont believe anyone who runs a website should have to depend on such a poorly run hosting company as hosttyme.
Apache was recompiled along with mysql and that didnt quite go to plan. During the process of backing up neowin for transfer over to the "new" server(which we have since learned, is not even our own, but belongs to someone else) they not only wiped all staff email accounts ( they have done this to us 4x) but also managed to wipe all sub-domains, passwords, and permissions were messed up. We can no longer edit, delete, or otherwise replace anything in /public_html/ as they are now somehow protected. I am guessing permissions were screwed during the transfer to the new system. CHMOD does not work on any files. So, not only has hosttyme proven themselves to be an extremely incompetent hosting company, but also, that they have little or any knowledge in the running, the maintainence or even configuration of a server. Neowin could have been back on its feet long before now, had their staff even an inkling of what to do.
If this were not bad enough, hosttyme then had the nerve to turn around and blame our own admin for the demise of the neowin server. Like installing mysql/php ever proved destructive to a server.... They then went on (and the nerve of them!) to ask our own members, without our permission for $5000 to purchase us a new server. (not including rack or bandwidth costs) Hosttyme has further stated, and publically that they no longer want us emergency paging them. Now you tell me. When they have taken to ignoring emails, and filtering those out from neowin, then what else are we supposed to do? The problem is theirs and they refuse to acknowledge it. Bad enough that they refuse or simply dont know how to repair neowin, yet they lay the responsibility on our own shoulders.
Time and time again they have argued that the problem of neowins high server loads were its members, or vbulletin, or mysql or even our graphics fault. All arguments which we have easily dismissed as ludicrous mind you. There are many sites out there running on far less than us and yet exist quite happily. We constantly made cut backs to neowin. We cut features, we trimmed back front page articles from 25 to 15, optimised and tweaked code,removed graphics, cut new registrations, disabled guest access, disabled welcome messages and much more. All of this had little effect. We even made a switch over to ibf board at one stage to prove it was NOT neowins fault. Hosttyme refuse to acknowledge this.
So, as you can now undoubtedly see. With this kind of mentality behind its staff, it is not hard to see why we are having so many problems. As it stands, neowins future right now is and i am sorry to say it, uncertain.
Unless Hosttyme starts taking some responsibility for its actions and begins to show more concern and support for those under its care, then neowin may remain down indefinitely.
Thanks for supporting neowin.net
Keldyn M.
Neowin Staff