unix16

[mattkakuk]

Guys. I wrote here a couple days ago and people jumped on me while vortech acted very cool to see a problem. Anyone sees the problem now?

[matthewshull]

I think if we opt to move the accounts we should get $4 credit for having to create a new account.

[matthewshull]

Originally Posted by mattkakuk

Guys. I wrote here a couple days ago and people jumped on me while vortech acted very cool to see a problem. Anyone sees the problem now?

I'll stick with Vortech thanks. Go to any other shared/reseller host and see if you get the support and response you get here, especially for the price. And major problems are not the norm. It happens from time to time. No matter where you go.

Now, with that said, problems like UNIX16 cannot be had. So let's kick this one in the butt and get it resolved!

[mattkakuk]

I did not say anything about leaving only that I see a problem with support.
This is not acceptable. It should have been junked 2 weeks ago.
All I know I am opening a back up account.

[nhdonny]

Well Said MatthewShull


"Now, with that said, problems like UNIX16 cannot be had. So let's kick this one in the butt and get it resolved!"

[matthewshull]

I see it is up now. Sure would like to hear what the problem was. Perhaps (crossing fingers) that it wasn't related to the other issues we have had?

[nhdonny]

I hate to say this is beginning to feel like Dejavu from an old home that Awen and I vacated. I sure hope not but reading some stuff on the wht and other places makes me very nervous right now.

[bubba]

Okay now I have to do something with at least one site on 16.

Would Craig or Brad please make a comment on whether we should move our accounts to another server or if we are near the solution to the problem?

What I want to know is if the box will be repaired or replaced right away or if the plan is to continue to trouble shoot the problem while running live sites.

What would Vortech do if their main vortech sites we on this server?

Just tell us the facts and we will make our decision accordingly.


Thanks,
b

[mattkakuk]

I agree with bubba, no hard feelings, just the facts please

[matthewshull]

I would also like to know now while I am in development. I would hate to move after we went live with the site.

[byron]

From what I saw when we last had to restart Unix16, something else besides Apache had managed to bind itself to the www listening port. You know, good old port 80. When Apache wouldn't restart by command line normally, we restarted the box.

We've been extremely busy with Unix16 lately, and have already made some internal switching with hardware and such. (We aren't using the same exact Unix16 we started with in the beginning.)

[ixie02]

Originally Posted by matthewshull

I would also like to know now while I am in development. I would hate to move after we went live with the site.

I am also currently developing 2 sites and unfortunately they are on unix16. What makes it worse is that my client is approving each page as I complete them. Obviously they are very unhappy about the server and of course me. I want to move them as soon as possible. Is unix16 still blocked from new sign ups and if everyone is moving will the other servers just get overloaded?

[byron]

I just checked, and Unix16 is currently turned *off* for new signups right now.

[admin]

ixie02 from what I under stand unix16 has had one reboot in the last 24 hours. I think the techs are getting it under control. There is no need to move your site. Since the 4th this is all of the down time for that system:
Apr 05,2005 09:43 PM Apr 05,2005 09:56 PM 13 Mins 51 Secs
Apr 07,2005 05:44 PM Apr 07,2005 05:46 PM 1 Mins 55 Secs

Not what I like to see, but still not bad really. The system if not already stable will get even more stable.

[Vixen]

Originally Posted by bubba

What I want to know is if the box will be repaired or replaced right away or if the plan is to continue to trouble shoot the problem while running live sites.

Thanks,
b

Bubba,

Unix16 has been replaced. It has been moved to a totally different server with totally different hardware, therefore we know the hardware is not the issue. Trust me, if I knew how to get the thing fixed I would have done it by now because I am personally tired of hearing about this machine.