I've had all sorts of issues in setting up load-balanced servers... for example:

- Actually ordering the servers took about 2 days of trouble tickets, phone calls, reordering, and confusion on ev1server's part...

- When the servers were finally ordered, EV1 put the wrong IPs in their system for the servers and I couldn't do anything with them.

- I can't edit the rDNS entires for the load-balanced servers.. I get an error about the subnet not being "fully configured". Each time EV1 says the problem is fixed, but it's not and I have to open up a new trouble ticket...

My two cents: EV1 shouldn't close a trouble ticket until they verify the problem is fixed! :confused:

Robert

Hello Robert,

I am sorry for any trouble you have had with your Load Balanced cluster.

I would like for my Customer Care team to look in to this issue for you, but I do not see an open case regarding this and I do not currently know your account number.

If you can, please email your account information to customercare@ev1servers.net with a very brief description of the problem (actually, what you put in this post would be perfect) we will be very happy to follow up on this issue for you.

Please remember that our forums are not an actual avenue for support, and to ensure the fastest response time to any issue you will want to follow up on any ticket first by contacting Support via our LiveSupport system, and then by working with Customer Care.

THIS HAPPENS WITH Ev1 SOME TIMES,BUT ONCE THE SERVICE IS SETUP IT RUNS SMOOTH.MOSTLY THIS HAPPEN DURING SETUP PHASE ONLY.

Hi,

Everything was running great for a while until:

- Trouble ticket opened saying my server was taking 67.15.175.111 from 67.15.175.38 even though 67.15.175.111 should be assigned to me for my load-balanced server

- I called EV1 tech support and they said the problem would be fixed for me shortly

- I chatted online with EV1 tech support and they said that MY server had stolen the IP. I told him that it was a load-balanced server with 4 ips assigned to it, 110 -> 113

- I updated the trouble ticket with my IP matrix assigned to me when i purchased the load balanced servers

- EV1 closed the trouble ticket saying that the IPs are not assigned to me

- I reopened the trouble ticket saying that the IPs ARE assigned to me since they're part of a load-balanced solution

- I called EV1 customer service, they transfered me to the wrong department

- I was then transferred to technical support, she wanted to transfer me to customer service, I refused and asked her to put my old IPs back on my account. She said she would have to transfer me to customer service to add more additional ips to my account. I explained that i don't want more additional IPs, I want my old load-balanced Ips reassigned to my server...

- She told me that everything would be fixed, I told her to stay on the line and ensure my old IPs are put back on the account. She said she couldn't do that. I hung up

.. still waiting. going to my websites loads up a default cpanel page on some one else's server.. ouch.

I have private messaged TechieSurfer hoping he can explain to his staff what a load-balanced server is... (Sorry for the sarcasm but dealing with EV1 is frustrating)

I cannot find the Customer Care email ticket related to this issue, but our Technical Support manager notified me about the specifics of this issue, so I am looking in to it now.

Robert,

I apologize for any hassle that this has caused you. I have checked with our Customer Service and Networking team and we are ensuring that all of your IPs are assigned correctly. At this time, it appears that your IPs have all been routed correctly. If this is not the case, please contact me directly at aaron@ev1.net so that I can continue to follow up on this for you.

Hi Aaron,

I just sent you an email. It is not working:

[root@sea root]# ifup eth0:1
Error, some other host already uses address 67.15.175.111.

I'm glad you're looking into this. Just as a double-check, please ensure that ALL these IPs are properly assigned to me so we don't run into this problem again:

67.15.175.110
67.15.175.111
67.15.175.112
67.15.175.113
67.15.175.114
67.15.175.115
67.15.175.116
67.15.175.117
67.15.175.118
67.15.175.119
67.15.175.120
67.15.175.121

It looks as though the IP is now pointing properly to my server

Thanks Aaron!

Robert

In continuation of this, I am facing an issue:

our servers are on 67.15.92.X1 and 67.15.92.X2

The load balancer is on 67.15.92.YY

When we hit the servers direct, pages load normally.

When the loadbalancer is hit, it does not respond.

We have taken this under the "High Availability Clusters" package

This issue is going on since Thursday and EV1 support is just issuing us blind answers without investigating the issue.

Aaron, I have mailed you the ticket.

Namaste,

I am very sorry to hear you are having a problem withour Load Balanced pair of servers. I'm sure we can get this issue addressed quickly, however I have not received the email you mentioned.

We will try to locate your account from the IPs listed, though with only partial IPs that might be difficult.

If you can email customercare@ev1servers.net with the same information you emailed me directly, we will get this issue addressed asap.

Namaste -

I investigated this issue and it appears we have identified your problem and have provided you with enough information for you to resolve the issue.


> This issue is going on since Thursday and EV1 support is just issuing us blind answers without investigating the issue.

With all due respect, it appears to me that the responses to your ticket were well thought out and contained plenty of relevant testing and supporting data.

The delay between Thursday and today was our engineers simply waiting for answers.


Randy Williams, CTO

Thank you very much. The issue has been resolved.

I'm posting the solution below for the benefit of forum members:

So following that logic, it makes sense that your server is trying to make a TCP connection with 67.15.92.YY. This will never work. A server being loadbalanced cannot make a connection to the load balancer IP itself...

Therefore if you change the application to not try this TCP connection (to itself through the loadbalancer??) your problem should then be resolved.