Joined
·
3,877 Posts
Because the previous thread got badly side-tracked I am opening a new one by re-iterating the situation. Looks like some members still have problems in accessing the forum. If so, please reply to this thread.
=======================================
...what engineering designed, what sales sold and what was installed?
I was so please a week ago when moving the database to a separate server seemed to solve the nagging performance problems. Little did I know that the ISP configured a distributed server over public Internet, and after a few days started billed me $80/day for the traffic! Their technical people and the salesman were well aware of customer's need, but the word did not get to implementation people.
That is why we had a interrupt in service yesterday when we configured a new system with the two servers in the same room and sub-net to avoid additional extra-orbital traffic charges for intra-traffic. We had to do this in hurry to avoid going bankrupt because of the charges. Unfortunately I was committed to be away for the week-end which did not make matters easier. The SOTW tech guru (my son) did remarkable job in configuring one more server. The access to the forum came back when the new IP address started to propagate. What was said above forum.saxontheweb.net vs. saxontheweb.net/vbulletin was a temporary phase before all necessary parameters were re-set. I still urge you to use forum.saxontheweb.net for accessing the forum because it will be more resilient in possible future changes.
A 60+ minute interrupt in service about two hours ago may have been independent of the other recent changes. Anyway the reason for it was removed.
I apologize for the inconvenience and for the lack of earlier communication. I could not get access to the net yesterday from the facility I normally use at the country-side. Maybe because of that the admin (at) saxontheweb.net inbox is full of messages from concerned and worried members. I apologize that I am not going to reply to them. I hope that people will find this message.
Our monthly charge went up by 250%, but hopefully now the traffic charge will be under control.
=======================================
...what engineering designed, what sales sold and what was installed?
I was so please a week ago when moving the database to a separate server seemed to solve the nagging performance problems. Little did I know that the ISP configured a distributed server over public Internet, and after a few days started billed me $80/day for the traffic! Their technical people and the salesman were well aware of customer's need, but the word did not get to implementation people.
That is why we had a interrupt in service yesterday when we configured a new system with the two servers in the same room and sub-net to avoid additional extra-orbital traffic charges for intra-traffic. We had to do this in hurry to avoid going bankrupt because of the charges. Unfortunately I was committed to be away for the week-end which did not make matters easier. The SOTW tech guru (my son) did remarkable job in configuring one more server. The access to the forum came back when the new IP address started to propagate. What was said above forum.saxontheweb.net vs. saxontheweb.net/vbulletin was a temporary phase before all necessary parameters were re-set. I still urge you to use forum.saxontheweb.net for accessing the forum because it will be more resilient in possible future changes.
A 60+ minute interrupt in service about two hours ago may have been independent of the other recent changes. Anyway the reason for it was removed.
I apologize for the inconvenience and for the lack of earlier communication. I could not get access to the net yesterday from the facility I normally use at the country-side. Maybe because of that the admin (at) saxontheweb.net inbox is full of messages from concerned and worried members. I apologize that I am not going to reply to them. I hope that people will find this message.
Our monthly charge went up by 250%, but hopefully now the traffic charge will be under control.