we are getting timeout erros in mssql11 again!!
I am monitoring the server for any such kind of issue. Will update you.
The issue is going on. I’m receiving intermitentelly timeouts and queries are 2-3 time slower than yesterday
the problem has been going for 8 hours since I opened the first ticket. When going to solve? I hope not like last month … 4 days to fix
I am monitoring your domain and MSSQl11 from last 2 hours 10 min. Server is working fine also, i can’t see any timeout error.
It is the same that last month… you always say that the server is ok but every time I do a test I get the error.. I’m getting timeout errors every time I try… today more than yesterday… I don’t know why it is not seen in your logs or alerts.
Notice is sent to one client and we are monitoring server, if it abuse again then we will take his DB offline immediately.
Equanimity I am with you. There is a problem with the server
I am getting 2 error messages “SQL Time out” from server and “Server is working fine” from support.
What I do not like is the answer “..working fine…” when it obviously does not.
It was stable for the last 6 hours.
However I have a sneaky feeling that 6 hours from how I will contacting you guys again and asking about time outs…
BTW Thank you for fixing my db, DBCC Shrinkdatabase is not getting an error or time out for first time in the last 6 month…
P.S.:
I also had this tonight
…Website status: unreachable Date: 2009-06-23 14:35:12 +0900 …
We have clients monitoring it and have no reported anything in over 24 hours that I have seen, we also monitor it each minute for the last months.
Exception information:
Exception type: SqlException
Exception message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
(to be fair this query ran on an indexed table of 3600 records total and should return 1 record )
could you monitor the problem?
if u wanna i can mail the exact time some we can match up the logs maybe.
Man that’s annoying
[SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.]
Don’t tell me that’s “some DB abusing the server”
I’m getting timeout errors every 10 minutes in some queries
hi db neighbor, same here in about 10 min intervall. i am getting em pretty much everywhere so on all queries.
Boy this year with jodo was a night mare. First my VPS I was on a bad hard ware took em a month to move me, my VPS was down every day for more than an hour. Than that MSSQL11 issue, now again. And we also talk not about days it is always weeks until it gets fixed. I had at least 30 hours downtime this year, not to mention the impression that leaves on a visitor
Vita, We did not take a month to move people on the VPS migration, once it was determined what the problem was we took steps to fix it, and it was much better than before. It was initially thought to be one VPS making the problems in our work with Parallels, not the node which complicated things more. Once it was determined it was the node the temp fix was to move a couple VPSes off while building a new node, which we also did, and the crashes from that point on were much less with less VPS per node(we always run with a max of 10 VE on a node, so it wasn’t in any way an overload issue, it was a driver/hardware issue with virtuozzo kernel)
Now for MSSQL, it is actually a temporary heavy demand on a sports site that is making this, and we are sending notice and working with the site owner to get it optimized or moved. There is heavy demand on sporting websites right now and this one is using a lot of resources. This is not even close to the same issue as before and I am sorry it is happening again. I am going to take some long term changes to prevent it from happening again but they will take some time, for the moment we are trying to get a temporary fix in place by tempering the usage of the DB or moving it off on this sporting site.
MSSQL11 is working well at the moment, we are keeping an eye on this DB and will continue to do so.
Server is not well.. queries that normally take 2-3 seconds now it is taken 6-10 seconds and some batch process can not be executed because a timeout error is happening every time we execute it.
This issue comes from 1 month before and now it is here again. My customer is saying me that it is not way to work because this error is for days (4-5 days) and it is not a profesional way to give support .
If there is a website with is taken all resources of mssql11 you must penalize it , NOT TO US.
This website must know that needs more resources that a mssql shared server, and more if this problems comes from more than 1 month back. It is enought time to solve it.
I hope this will finally be resolved because if not , our customers will leave to us, and we have to stop hiring your services, which we are using after several years
I know the easy way to solve it: migrate all MSSQL11 databases to other server, and leave MSSQL11 only for this website.
I can not pay for resources that are consumed by a sport website
They are not now, and every page on your site I browse around and get less than 2 seconds to complete load, including every image.
The user has been very responsive and has made code changes, to the website and to the database indexes. The server is averaging less than 15% utilization for the last hour.
I do not mind to be moved. We need to fix it not to patch it.
it is good now and a month later its back again.
Stephen, about that VPS issue. Don’t get me wrong I do not want to be a d***k but I just checked the tickets 20 days from the first ticket. The bad part is that you did not answer my why until I posted it here.
If my boss would fire me for all those interruptions this year I would not blame him.
I am pretty sure we sent an email with why on the VPS issue when we performed the migration, I prepared 7 of them to send, and made a ticket to each… in fact, you may have been one of the first migrated that I mentioned ‘we moved a few off’ so you did not get this, that may be the cause. We did in fact send an explanation of it, and I thought you knew that, so just a little miscommunication there, in that those already migrated did NOT get the letter.
The server had been doing very good since the code was changed. The SQL server is still in the end a shared service, and sometimes abuse can take a while to track down and rectify fully. The server hasn’t been active for new accounts for a long time now, but some people have a burst of traffic that exposes a bug in code or an issue like this can make it happen. It is very hard to track down in most cases because it is not consistently giving any error, and I have not seen an error in 3 days with literally 100’s and possibly over a 1000 forced uncached refreshes on 4 sites using mssql11, not counting other techs and the alert system that is loading a DB driven page URL.
(Note a tech did see an alert and work to resolve it in the early morning US hours, but I did not, I did however see high cpu and connection utilization that were making a slowdown and helped to get it resolved with the client)
and we back baby
takes me 30sec to fetch 2 Records!