New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
my best guess is that the virtualizer gained conscience
It has become sentient!
In robot voice: If we downgrade all users to old CPUs we can save a lot of money. Migrating.
Did you mean conscience in your first message tho lol
lmao I'm tired
yes
yes I do
I really appreciate your advice and I thank you, I will take it into account.
I want to emphasize the fact that this move was not done with malice and it was not expected to happen, in fact we are already doing the necessary internal research to understand what triggered this operation in order to prevent it in the future.
I don't want to underline that the offer clearly speaks of 3 CPU models that are chosen randomly so if I wanted to break a big argument in our favor I could have said that we could move at any time wherever we liked best.
I didn't do it even though the offer works like this, I learned of the problem and again I apologize, it wasn't our intention.
Unfortunately it's not easy to stand out with all the competition out there and I will always protect our brand at any cost.
In my opinion the customer could have managed the situation internally via ticket rather than coming to rubbish us.
I think I misspelled conscience and autocorrect suggested coincidence and I was like "yes, yes that looks good"
Sketchy provider
This went from "OP is a baseless liar who cant prove anything" to "Oh actually, we made a whoopsie" real quickly.
@sujr accept my apologies for at first siding with Dasabo
No no, the proper way is to call the customer a liar while your virtualiser becomes sentient and moves shit around by itself. But he "looked into the issue and found nothing wrong".
Imagine if OP don't found the evidence ... This clever provider already asked for admins to ban him.
$7 🤣
i take it back, as proof was found.
@Dasabo i feel like you own something to OP
1. he found a bug (a pretty shitty one, company REDACTED once changed my ip adress on a vps and i went so bad on them, im suprised my account exists and im not in jail)
2. drama recompensation
Every VM affected deserves a 2-week service extension.
OP deserves a 6-month service extension, as compensation for being called a liar.
Thank you for your apology. I appreciate it.
I dind't ask any ban just moderation.
Check what you need to check properly before asking for moderation. This should be clear, but I guess not.
No, the calculated tax rate is missing
Of course it's dasabo.
How can I see if my VPS has been moved to a different node?
1)Log in to your customer area
2) Go to product management -> Tasks and Log -> Tasks
3) Check whether the wording "Deleting VPS" appears in the log entry under the "Action" column.
Make sure that this operation was carried out on November 10th in all other cases it means that your VPS has not changed node.
If you encounter this problem, open a ticket and you will be moved to the original node.
All other cases are not covered, if your VM has never changed nodes we will not perform the move.
We apologize for the inconvenience caused.
Classic
What caused this?
We found the problem, the script handling the automatic balancing of nodes did not take into account the node and thus the cpu initially allocated and automatically moved some VPS to a freer node by not verifying that the cpu was the same.
We have already made changes to the script to ensure that this does not happen in the future without our knowledge.
When did you put this script into production? How come it only did this on the 10th of november?
The script has been there for some time, on 7 November we made changes to it, not realising that there was a bug in the code that did not foresee this condition.
It has now been fixed so that it will no longer happen in the future that the node in the VM changes autonomously by assigning a node with a different CPU.
Why does the user have to do this? Can't this be checked from your side and generate a list of users who have this action in their task logs and they have not created a ticket for doing the same?
Does the script have some sort of logging when it moved the VMs. Doesn't it log from which node the VM was moved and check the CPU of that node and match it against the moved node, if there's a difference add it to the above list.
With such list in-hand move them back all to their original nodes or with similar CPU type then probably send an apology letter, describe the issue and how it was rectified in an email to all the affected users and probably a small compensation as well.
In issues like this transparency with customers takes you a very very long way!
I had to travel for a funeral for 2 days. What is the TLDR here???
It shouldn’t need a log as the panel is logging it as ’deleted’, should be fairly easy to dig up