Website issues?

Nodin

Overheal wrote: »

Something's wrong with the G-Diffuser! Do a barrel roll!

No, they need to reverse the polarity and then route it through the main deflector array.




Or turn it off and then on again.

ardinn

Check the Flux Capacitator

Overheal

Nodin wrote: »

No, they need to reverse the polarity and then route it through the main deflector array.




Or turn it off and then on again.

Well, you can only encode the Chevrons if you use a direct current... so yeah.

OldGoat

Overheal wrote: »

Well, you can only encode the Chevrons if you use a direct current... so yeah.

Direct current! So thats what it is. I always asumed that AC/DC was Alternating Current/Dilithium Crystal

mike65

At it again, seems to get worser in the evening.

GLaDOS

Aye, struggling to load pages

Conor

mike65 wrote: »

At it again, seems to get worser in the evening.

Especially mysterious since it's the busiest time of the day.

:rolleyes:

mike65

Don't get smart, the site is verging upon unusable at times.

Conor

mike65 wrote: »

Don't get smart, the site is verging upon unusable at times.

And you think myself and Ross are sitting on our holes doing nothing?

We're working on it. If it was easy, it would be fixed already.

mike65

Fine, thats all you needed to say.

Overheal

give it 30ms... CLEAR!



Okay, it's breathing again.. o_O

Sully

Still timing out here. Can we just block access to the Galway forum Conor?! :P

Fago!

It keeeeeeeps happening to me. It took me 5 minutes to post one post!

Yo Buddy. You still alive?

Probably time to reach out to the community to help with added servers etc,

:pac:

I lol'd

OutlawPete

Fago! wrote: »

It took me 5 minutes to post one post!

In fairness, you could do with five minutes contemplation on your posts

dlofnep

I ran a few traceroutes. Results are not consistent.

Traceroute 1:

Tracing route to loadbalancer.boards.ie [89.234.66.107]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 38 ms 5 ms 10 ms 10.92.240.1
3 29 ms 24 ms 14 ms 089-101-175078.ntlworld.ie [89.101.175.78]
4 14 ms 15 ms 14 ms to-inex-dub-deg-gw.digiweb.ie [193.242.111.20]
5 20 ms 13 ms 18 ms ip-89-234-66-107.dedi.digiweb.ie [89.234.66.107]

Traceroute 2:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 15 ms 6 ms 10.92.240.1
3 44 ms 13 ms 27 ms 089-101-175078.ntlworld.ie [89.101.175.78]
4 169 ms 204 ms 203 ms to-inex-dub-deg-gw.digiweb.ie [193.242.111.20]
5 * 19 ms 12 ms ip-89-234-66-107.dedi.digiweb.ie [89.234.66.107]

Traceroute 3:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 5 ms 6 ms 7 ms 10.92.240.1
3 21 ms 14 ms 18 ms 089-101-175078.ntlworld.ie [89.101.175.78]
4 42 ms 27 ms 15 ms to-inex-dub-deg-gw.digiweb.ie [193.242.111.20]
5 * * * Request timed out.
6 * 13 ms 11 ms ip-89-234-66-107.dedi.digiweb.ie [89.234.66.107]

Having issues pinging the server too - alot of packets are dropping.

Ping Request 1:

Pinging loadbalancer.boards.ie [89.234.66.107] with 32 bytes of data:

Request timed out.
Reply from 89.234.66.107: bytes=32 time=12ms TTL=60
Reply from 89.234.66.107: bytes=32 time=13ms TTL=60
Reply from 89.234.66.107: bytes=32 time=13ms TTL=60

Ping statistics for 89.234.66.107:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 13ms, Average = 12ms

Ping Request 2:

Pinging loadbalancer.boards.ie [89.234.66.107] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 89.234.66.107:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Hope these help.

epgc3fyqirnbsx

Have you checked the batteries?

themadchef

Conor wrote: »

And you think myself and Ross are sitting on our holes doing nothing?

We're working on it. If it was easy, it would be fixed already.

No need to be so ratty about it. Try sharing the pain, we arent expecting miracles out of yee but it wouldint hurt not to bite the heads off the posters who are providing feedback.

We get it, it's not easy to fix, hope yee find a solution.

DublinWriter

Dakota Green Mop wrote: »

Have you checked the batteries?

Have you rebooted?

FFS, just go away and re-write VB in the next ten minutes, no, make that five. While you're at it, re-write a better Php engine and backend clustered DB.

...and Marketing says it that it must be 'cloudy'. And come in a blue box.

Overheal

DublinWriter wrote: »

Have you rebooted?

FFS, just go away and re-write VB in the next ten minutes, no, make that five. While you're at it, re-write a better Php engine and backend clustered DB.

...and Marketing says it that it must be 'cloudy'. And come in a blue box.

If Kira Yamato can write a new operating system for a Gundam while he's being shot at, that should be relatively easy.

Conor

themadchef wrote: »

No need to be so ratty about it. Try sharing the pain, we arent expecting miracles out of yee but it wouldint hurt not to bite the heads off the posters who are providing feedback.

Sorry, but at the moment I'm running on 4 hours sleep since Sunday thanks to this problem and Ross helped last night even though he's on holidays. And while I appreciate that ye're trying to provide feedback, we have way more information at our fingertips that ye do, so the absolute number one best thing you can do is not complain (cos that stresses me out).

Unless you really, really know the internals of networking on FreeBSD there is absolutely nothing ye can do to help more actively than that.

themadchef

Conor wrote: »

Sorry, but at the moment I'm running on 4 hours sleep since Sunday thanks to this problem and Ross helped last night even though he's on holidays. And while I appreciate that ye're trying to provide feedback, we have way more information at our fingertips that ye do, so the absolute number one best thing you can do is not complain (cos that stresses me out).

Unless you really, really know the internals of networking on FreeBSD there is absolutely nothing ye can do to help more actively than that.

Sorry for your trouble Conor.

Silly suggestion but if you dont want feedback lock it up and plain old "we know, broken, dont go on about it" sticky till you get the problem fixed. That way no one ends up on the wrong end of a rant

Conor

themadchef wrote: »

Sorry for your trouble Conor.

Silly suggestion but if you dont want feedback lock it up and plain old "we know, broken, dont go on about it" sticky till you get the problem fixed. That way no one ends up on the wrong end of a rant

Myself and Dav did think about that, but given our experience with the time we had search turned off it's more trouble than it's worth.

Daemos

Yo Buddy. You still alive? wrote: »

Probably time to reach out to the community to help with added servers etc,

:pac:

I lol'd

Good because no one else did :pac:

Cheers for the effort Rossnor, you'll find those little gremlins eventually

Slidey

Maybe it is the traffic dying down but things seem to have improved in the last 15 mins or so

Fago!

OutlawPete wrote: »

In fairness, you could do with five minutes contemplation on your posts

NEVER gonna happen!

Sully

Conor wrote: »

Sorry, but at the moment I'm running on 4 hours sleep since Sunday thanks to this problem and Ross helped last night even though he's on holidays. And while I appreciate that ye're trying to provide feedback, we have way more information at our fingertips that ye do, so the absolute number one best thing you can do is not complain (cos that stresses me out).

Unless you really, really know the internals of networking on FreeBSD there is absolutely nothing ye can do to help more actively than that.

According to Digiweb, the majority of their technical support calls are fixed by a simple power cycle of the modem.

So Conor, have you rebooted the modem?!?!

Insect Overlord

They're probably trying to fix it without taking the site off-line...

Conor

Sully wrote: »

So Conor, have you rebooted the modem?!?!

If only I could find it.

Overheal

Conor wrote: »

If only I could find it.

Oh dear: he's gone delirious from exhaustion.