Report Problems/Questions Here

[RTH10260]

Just returned again, a few hours ago I also got those DB error messages. My guess is that tech support was fiddling with the DB. Foggy would have known how to set the forum to the maintenance mode message beforehand.

Did I already say that the forum looks real snappy now?

[northland10]

I had an error as well and now it is snappy. Somebody may have been bouncing servers.

[neonzx]

Yeah 1 1/2 hours or so of the SQL connection failure -- not just the phpbb but the site homepage, which is wordpress.

FOR THE MOMENT, it seems to running fine.

If runs good for 24-hours, I will call it a successful fix.

[much ado]

Yes, behaving really well now.

[Reality Check]

Yeah 1 1/2 hours or so of the SQL connection failure -- not just the phpbb but the site homepage, which is wordpress.

FOR THE MOMENT, it seems to running fine.

If runs good for 24-hours Scaramuccis, I will call it a successful fix.

FIFY

[RTH10260]

Refreshing that at leaset for one hour again things are running smoothly.

BUT.... But... but... ...... I don't anymore get the time to make cofeve between replies

[sugar magnolia]

Did we ever find out what the real issue was?

[Maybenaut]

Keeping my fingers crossed.

Meanwhile, I’m using the up time to catch up on threads of lesser interest. Since all this started I’ve only kept up moth my three or four most favorite threads.

[Reality Check]

I wouldn't call it fixed but better than it has been. I am still seeing hangs of more than 5 seconds when changing pages.

[neonzx]

I wouldn't call it fixed but better than it has been. I am still seeing hangs of more than 5 seconds when changing pages.

Experiencing same. Along with a few timeouts.

[Reality Check]

Experiencing same. Along with a few timeouts.

It is getting worse and back to almost unusable.

[RTH10260]

Who tripped and dropped that open glas of molasses over the server

[RTH10260]

Remote armchair problem analysis: earlier in the day the database was offline, and I guess its server got rebooted, possibly also the webserver machine. Then everything was fast. Now sludging along again. My best guess at this time that there is a component with memory leaking, eg acquired memory blocks are not released back after use. Now the software is jugling with the remaining memory and discards cached data to manage what it has.

[northland10]

Who tripped and dropped that open glass of molasses over the server

I strained my back the other day doing the dangerous activity of drying a foot (old muscle strain likes to return and remind me I did something stupid 30 years ago). Therefore, I have been walking differently, and thus, I tripped and dropped the glass. Sorry folks.

In the past, I have been accused, maybe rightfully, of bringing some servers to a crawl. When doing data analytics, that can happen sometimes, especially if you have not designed your servers to handle the pulls that some of us need to do.

[Reality Check]

I have a new theory on the issues with the Fogbow. The server is powered by a squirrel in a cage. When the squirrel is frisky and runs it works fine. When it gets tired it comes to a halt. It explains the observed behavior perfectly.

[neonzx]

I have a new theory on the issues with the Fogbow. The server is powered by a squirrel in a cage. When the squirrel is frisky and runs it works fine. When it gets tired it comes to a halt. It explains the observed behavior perfectly.

Good as any guess I have heard thus far.

[sugar magnolia]

The squirrel is exhausted.

[bill_g]

My squirrel snorted some magic peanut dust, and is keeping a top pace without breaking a sweat.

[neonzx]

My squirrel snorted some magic peanut dust, and is keeping a top pace without breaking a sweat.

Give it time, bill...

[Tiredretiredlawyer]

Squirrel!!

[Reality Check]

Rocky is on the job this morning.

[neonzx]

Rocky is on the job this morning.

Looks like you spoke too soon. Our squirrel needs another cocaine bump.

[bill_g]

Rocky is on the job this morning.

Looks like you spoke too soon. Our squirrel needs another cocaine bump.

Still rockin-n-rollin over here.

C:\Users\Bill>tracert thefogbow.com

Tracing route to thefogbow.com [199.250.206.89]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 2 ms 2 ms 2 ms 192.168.254.254
3 18 ms 18 ms 19 ms adr01.tgrd.or.nwestnet.net [50.46.181.54]
4 20 ms 25 ms 19 ms cr2-tgrdorxa-a-be-501.bb.as20055.net [64.52.97.62]
5 24 ms 23 ms 23 ms cr2-bvtnorxb-b-be-25.bb.as20055.net [198.179.53.92]
6 22 ms 23 ms 24 ms cr2-bvtnorxb-a-be-10.bb.as20055.net [107.191.236.97]
7 23 ms 23 ms 22 ms cr2-smrworxa-b-be-17.bb.as20055.net [107.191.236.120]
8 23 ms 23 ms 23 ms cr2-smrworxa-a-be-12.bb.as20055.net [107.191.236.113]
9 24 ms 24 ms 23 ms prm1-sttlwawb-b-be-15.bb.as20055.net [107.191.236.62]
10 * * * Request timed out.
11 25 ms 22 ms 23 ms 76.74.79.9
12 87 ms 94 ms 89 ms ae36.cr5-was1.ip4.gtt.net [89.149.181.50]
13 86 ms 85 ms 86 ms edge2.iad1.inmotionhosting.com [198.46.80.11]
14 86 ms 86 ms 86 ms edge2.iad1.inmotionhosting.com [198.46.80.11]
15 87 ms 87 ms 87 ms csw2.iad1.inmotionhosting.com [198.46.80.85]
16 86 ms 86 ms 86 ms eccomp4-havp12.inmotionhosting.com [104.193.140.63]
17 87 ms 88 ms 86 ms vps42141.inmotionhosting.com [199.250.206.89]

Trace complete.

C:\Users\Bill>ping 199.250.206.89

Pinging 199.250.206.89 with 32 bytes of data:
Reply from 199.250.206.89: bytes=32 time=86ms TTL=49
Reply from 199.250.206.89: bytes=32 time=87ms TTL=49
Reply from 199.250.206.89: bytes=32 time=91ms TTL=49
Reply from 199.250.206.89: bytes=32 time=86ms TTL=49

Ping statistics for 199.250.206.89:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 86ms, Maximum = 91ms, Average = 87ms

[neonzx]

Rocky is on the job this morning.

Looks like you spoke too soon. Our squirrel needs another cocaine bump.

Still rockin-n-rollin over here.

C:\Users\Bill>tracert thefogbow.com

Tracing route to thefogbow.com [199.250.206.89]
over a maximum of 30 hops:

Yeah, but bill -- a traceroute/ping is not giving you want you want. That is good to check routing problems or a screwed up NIC but not what is happening on the server itself. You'd have to perform a GET to request a page.

[RTH10260]

The ping / tracert numbers have never been a problem over The Great Pond either. It's the rodents run servers.