Luger forum unavailable several hours / day - Page 2

Edward Tinker · 01-05-2016, 08:11 PM

Quote:

Originally Posted by John Sabato

Mark, the "provider" is John D. The forum is hosted on his own servers and he normally announces system upgrades and software updates before they happen...

I have not personally experienced the types of outages that folks are reporting, ...not at home or at work... perhaps there is something that all those who have been reporting issues have in common? But I am not sure what that might be...

How many of these guys have broadband? I know a couple of folks have dial up?

DavidJayUden · 01-05-2016, 10:08 PM

High speed broadband here.

CAP Black · 01-05-2016, 10:24 PM

I now go to the two luger forums on Google Chrome and have no problems.
Jack

SailorBill · 01-06-2016, 02:22 PM

High speed broadband here

rhuff · 01-06-2016, 04:03 PM

I was having a similar problem as others here with the forum being out. I switched from Internet Explorer to Google Chrome, and have had no problems since the switch. I have high speed internet.

sheepherder · 01-15-2016, 07:16 PM

Just experienced a 'Network Timeout'. This is NOT the usual error msg I get ("forum.lugerforum.com not found") but it seems to be the one others are commenting on...

Now I'm getting it...

sheepherder · 01-22-2016, 06:41 PM

OK, just had the 'address not found' error msg. Not a timeout...No idea why...

Five minutes later, it's found...

markbritt · 05-03-2016, 08:17 AM

Forum Moderators:

The forum was down again yesterday afternoon around 4:30 pm Central time for about 45 minutes. If you go to the command prompt and issue a 'ping' command:

ping lugerforum.com

There are no replies from 72.71.199.44.

This morning forum is available and a ping command to 72.71.199.44 shows the board is up.

Mark

Edward Tinker · 05-03-2016, 02:19 PM

Mark, I am surprised that John allows a ping.

What seems consistent is that folks use www.lugerforum.com and fewer problems with
forums.lugerForum.com
Seems to me that folks should save the second one... . Also, I use Firefox and chrome....

Eugen · 05-03-2016, 02:25 PM

Quote:

Originally Posted by markbritt

Forum Moderators:

The forum was down again yesterday afternoon around 4:30 pm Central time for about 45 minutes. If you go to the command prompt and issue a 'ping' command:

ping lugerforum.com

There are no replies from 72.71.199.44.

This morning forum is available and a ping command to 72.71.199.44 shows the board is up.

Mark

Yes, I noticed that too. As a newbie Luger addict, I was beginning to feel inaccessible forum withdrawal symptoms. Yes, like when I don't get my morning coffee.

sheepherder · 05-03-2016, 03:33 PM

Quote:

Originally Posted by Eugen

Yes, like when I don't get my morning coffee.

Eugene/Donald [whatever] - I fixed your avatar!

...

mrerick · 05-03-2016, 09:09 PM

The problem with intermittent access may be the Internet Service Provider's Name Servers. In order for your computer to find the Lugerforum server's IP address, it has to convert the canonical address using a nameserver. It's done under the covers and normally invisible and fast.

Each ISP operates their own Name Servers, and something may be interfering with their operation.

When it fails, open a command prompt window and enter the command:

nslookup lugerforum.com

and see what happens.

Then try

nslookup forum.lugerforum.com

and see if that works.

If you have intermittent nameserver problems, you can manually add one that Google maintains. It is done in the network configuration for the network adapter on your computer. The Google nameserver is at IP address 8.8.8.8

Marc

cirelaw · 05-03-2016, 11:08 PM

I must admit having after having thousand posts, I have never noticed it down no more than a few times and each time I was given notice on the site! Thank You John and Ed for the privalege. Thank You all our Heros behind the scenes that makes my life even more enjoyable and for free!!!~~ Eric

markbritt · 05-04-2016, 09:15 AM

Marc:

While I agree with your statements on the name servers, I don't think this is the issue here. If you ping lugerforum.com, you should get a reply from 72.71.199.44. The local provider will resolve the lugerforum.com to 72.71.199.44. However, in this case, I pinged the server directly with 'ping 72.71.199.44' and there was no reply. There are no name server involved in this, so I do believe there is an intermittent issue with the hosting of lugerforum.com

Mark

mrerick · 05-04-2016, 09:39 AM

i just checked, and I do get ping responses from that static address.

During a failure period, try using "traceroute".

I'm on CenturyLink's ISP network locally in North Carolina. I route through:

embarqhsd.net (backbone)
quest.net (backbone)
cogentco.net (several nodes)
myfairpoint.net (several nodes - John's local ISP network)

During a failure, "traceroute" will tell you where the relay is failing on the way to John's local network.

Reliability and access to the forum from here is good. If I were to guess, I'd suggest something is failing on your side of a backbone connnection or in all the "cogent" and "fairpoint" nodes things route through...

Marc

sheepherder · 05-04-2016, 10:41 AM

Quote:

Originally Posted by cirelaw

I must admit having after having thousand posts, I have never noticed it down no more than a few times and each time I was given notice on the site!

I would estimate that I get the 'timeout' or 'notfound' error msgs (shown in my previous posts) about 2 - 3 times per week, on average. None has lasted more than an hour, most 5 - 10 minutes. Dial-up connection, Verizon TelCo.

John Sabato · 05-04-2016, 11:26 AM

Quote:

Originally Posted by markbritt

..., so I do believe there is an intermittent issue with the hosting of lugerforum.com

Mark

Mark, I don't think that can be the issue since John D. hosts this forum (and others) on his own high speed connection on his own business servers...

markbritt · 05-10-2016, 07:28 PM

Guys:

Hopefully this will assist in the troubleshooting. I am going to email these files to John S too. This morning at 6:30 am Central time I could not access the site. I attempted nslookup, ping and trace route commands and have the data. When I got home, I did the exact same steps when the site is up and running.

It is not a DNS issue with local providers. It is not a routing issue. I suspect there is something with the server (perhaps a backup that is causing the NIC card not to respond? Ive seen this).

LUGERFORUM DOWN:

C:\Users\mark>nslookup lugerforum.com
Server: UnKnown
Address: 192.168.100.1

Non-authoritative answer:
Name: lugerforum.com
Address: 72.71.199.44

C:\Users\mark>tracert lugerforum.com

Tracing route to lugerforum.com [72.71.199.44]
over a maximum of 30 hops:

1 16 ms 18 ms 18 ms 66.11.108.1
2 20 ms 19 ms 18 ms 208-103-3-97.static.indianafiber.net [208.103.3.97]
3 18 ms 19 ms 19 ms 69-160-211-21.static.indianafiber.net [69.160.211.21]
4 26 ms 24 ms 24 ms te0-0-0-1.nr12.b021117-0.ind01.atlas.cogentco.com [38.104.214.101]
5 27 ms 23 ms 24 ms 154.24.38.29
6 39 ms 38 ms 38 ms be2721.rcr11.cvg02.atlas.cogentco.com [154.54.28.134]
7 36 ms 38 ms 38 ms be2729.rcr21.cmh02.atlas.cogentco.com [154.54.40.170]
8 36 ms 39 ms 38 ms be2732.ccr21.cle04.atlas.cogentco.com [154.54.40.250]
9 44 ms 43 ms 63 ms be2878.ccr21.alb02.atlas.cogentco.com [154.54.26.130]
10 48 ms 48 ms 49 ms 38.104.52.78
11 50 ms 54 ms 75 ms burl-lnk-70-109-168-139.ngn.east.myfairpoint.net[70.109.168.139]
12 54 ms 53 ms 54 ms fttp07-pos1-0.cncdnh.fast.myfairpoint.net [64.222.166.111]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.

C:\Users\mark>ping lugerforum.com

Pinging lugerforum.com [72.71.199.44] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

C:\Users\mark>time
The current time is: 6:33:57.99
Enter the new time:

C:\Users\mark>date
The current date is: Tue 05/10/2016
Enter the new date: (mm-dd-yy)

LUGERFORUM UP:

C:\Users\mark>nslookup lugerforum.com
Server: UnKnown
Address: 192.168.100.1

Non-authoritative answer:
Name: lugerforum.com
Address: 72.71.199.44

C:\Users\mark>tracert lugerforum.com

Tracing route to lugerforum.com [72.71.199.44]
over a maximum of 30 hops:

1 15 ms 15 ms 18 ms 66.11.108.1
2 23 ms 18 ms 18 ms 208-103-3-97.static.indianafiber.net [208.103.3.97]
3 24 ms 23 ms 24 ms 69-160-211-21.static.indianafiber.net [69.160.211.21]
4 27 ms 23 ms 24 ms te0-0-0-1.nr12.b021117-0.ind01.atlas.cogentco.com [38.104.214.101]
5 23 ms 24 ms 23 ms 154.24.38.29
6 38 ms 38 ms 39 ms be2721.rcr11.cvg02.atlas.cogentco.com [154.54.28.134]
7 39 ms 38 ms 38 ms be2729.rcr21.cmh02.atlas.cogentco.com [154.54.40.170]
8 35 ms 58 ms 34 ms be2732.ccr21.cle04.atlas.cogentco.com [154.54.40.250]
9 43 ms 44 ms 44 ms be2878.ccr21.alb02.atlas.cogentco.com [154.54.26.130]
10 48 ms 48 ms 49 ms 38.104.52.78
11 51 ms 48 ms 49 ms burl-lnk-70-109-168-128.ngn.east.myfairpoint.net[70.109.168.128]
12 54 ms 54 ms 54 ms burl-lnk-70-109-168-131.ngn.east.myfairpoint.net[70.109.168.131]
13 53 ms 50 ms 52 ms pool-64-222-213-128.port.east.myfairpoint.net [64.222.213.128]
14 58 ms 54 ms 59 ms pool-64-222-213-133.port.east.myfairpoint.net [64.222.213.133]
15 113 ms 118 ms 115 ms fttp07-pos0-0.cncdnh.fast.myfairpoint.net [64.222.166.71]
16 66 ms 61 ms 64 ms static-72-71-199-44.cncdnh.fast07.myfairpoint.net [72.71.199.44]

Trace complete.

C:\Users\mark>ping lugerforum.com

Pinging lugerforum.com [72.71.199.44] with 32 bytes of data:
Reply from 72.71.199.44: bytes=32 time=153ms TTL=115
Reply from 72.71.199.44: bytes=32 time=668ms TTL=115
Reply from 72.71.199.44: bytes=32 time=436ms TTL=115
Reply from 72.71.199.44: bytes=32 time=62ms TTL=115

Ping statistics for 72.71.199.44:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 668ms, Average = 329ms

C:\Users\mark>

cirelaw · 05-10-2016, 08:01 PM

Thank You For All The Hard Work!!!

John D. · 05-11-2016, 04:21 PM

Seems a bit contradictory, as I use a third party monitor tool to watch my servers, FQDNS, circuits, individual sites, etc. Attached is the stat log from Lugerforum and the server. I've been in the IT industry since 1987 - and this site since 2001 - so, what do I know

If it's down for an hour or so - I'm usually backing up the DB, making a hardware change - whatever - so those downtimes are those I'm aware of?

Anyway - I'll continue to monitor the site. The triggers below poll the site every 5 minutes from seven locations around the world.

Thanks,

John D.

01-15-2016, 07:16 PM	#26
sheepherder Lifer Lifetime Forum Patron Join Date: Feb 2009 Location: ...on the 'ol Erie Canal... Posts: 8,183 Thanks: 1,400 Thanked 4,442 Times in 2,330 Posts	Just experienced a 'Network Timeout'. This is NOT the usual error msg I get ("forum.lugerforum.com not found") but it seems to be the one others are commenting on... Now I'm getting it... Attached Thumbnails __________________ I like my coffee the way I like my women... ...Cold and bitter...

01-22-2016, 06:41 PM	#27
sheepherder Lifer Lifetime Forum Patron Join Date: Feb 2009 Location: ...on the 'ol Erie Canal... Posts: 8,183 Thanks: 1,400 Thanked 4,442 Times in 2,330 Posts	OK, just had the 'address not found' error msg. Not a timeout...No idea why... Five minutes later, it's found... Attached Thumbnails __________________ I like my coffee the way I like my women... ...Cold and bitter...

05-03-2016, 09:09 PM	#32
mrerick Super Moderator - Patron LugerForum Life Patron Join Date: Dec 2009 Location: Eastern North Carolina, USA Posts: 3,909 Thanks: 1,374 Thanked 3,110 Times in 1,510 Posts	The problem with intermittent access may be the Internet Service Provider's Name Servers. In order for your computer to find the Lugerforum server's IP address, it has to convert the canonical address using a nameserver. It's done under the covers and normally invisible and fast. Each ISP operates their own Name Servers, and something may be interfering with their operation. When it fails, open a command prompt window and enter the command: nslookup lugerforum.com and see what happens. Then try nslookup forum.lugerforum.com and see if that works. If you have intermittent nameserver problems, you can manually add one that Google maintains. It is done in the network configuration for the network adapter on your computer. The Google nameserver is at IP address 8.8.8.8 Marc __________________ Igitur si vis pacem, para bellum - - Therefore if you want peace, prepare for war.

05-04-2016, 09:39 AM	#35
mrerick Super Moderator - Patron LugerForum Life Patron Join Date: Dec 2009 Location: Eastern North Carolina, USA Posts: 3,909 Thanks: 1,374 Thanked 3,110 Times in 1,510 Posts	i just checked, and I do get ping responses from that static address. During a failure period, try using "traceroute". I'm on CenturyLink's ISP network locally in North Carolina. I route through: embarqhsd.net (backbone) quest.net (backbone) cogentco.net (several nodes) myfairpoint.net (several nodes - John's local ISP network) During a failure, "traceroute" will tell you where the relay is failing on the way to John's local network. Reliability and access to the forum from here is good. If I were to guess, I'd suggest something is failing on your side of a backbone connnection or in all the "cogent" and "fairpoint" nodes things route through... Marc __________________ Igitur si vis pacem, para bellum - - Therefore if you want peace, prepare for war.

05-11-2016, 04:21 PM	#40
John D. Administrator & Site Owner LugerForum Patron Join Date: Jun 2002 Location: A Little NE of Somewhere... Posts: 2,651 Thanks: 477 Thanked 515 Times in 128 Posts	Seems a bit contradictory, as I use a third party monitor tool to watch my servers, FQDNS, circuits, individual sites, etc. Attached is the stat log from Lugerforum and the server. I've been in the IT industry since 1987 - and this site since 2001 - so, what do I know If it's down for an hour or so - I'm usually backing up the DB, making a hardware change - whatever - so those downtimes are those I'm aware of? Anyway - I'll continue to monitor the site. The triggers below poll the site every 5 minutes from seven locations around the world. Thanks, John D. Attached Thumbnails

01-05-2016, 10:08 PM	#22
DavidJayUden Patron LugerForum Patron Join Date: Nov 2008 Posts: 4,047 Thanks: 578 Thanked 1,414 Times in 887 Posts	High speed broadband here.

01-05-2016, 10:24 PM	#23
CAP Black User Join Date: Dec 2008 Location: Fairmont, WV Right here in Mountaineer country and God's country Posts: 767 Thanks: 100 Thanked 168 Times in 96 Posts	I now go to the two luger forums on Google Chrome and have no problems. Jack

01-06-2016, 02:22 PM	#24
SailorBill User Join Date: Feb 2013 Location: SF Bay Area Posts: 26 Thanks: 0 Thanked 9 Times in 4 Posts	High speed broadband here

01-06-2016, 04:03 PM	#25
rhuff Patron LugerForum Patron Join Date: Mar 2011 Location: Az. Posts: 2,291 Thanks: 2,709 Thanked 972 Times in 717 Posts	I was having a similar problem as others here with the forum being out. I switched from Internet Explorer to Google Chrome, and have had no problems since the switch. I have high speed internet.

05-03-2016, 08:17 AM	#28
markbritt User Join Date: Oct 2009 Location: NW Indiana Posts: 240 Thanks: 5 Thanked 48 Times in 22 Posts	Forum Moderators: The forum was down again yesterday afternoon around 4:30 pm Central time for about 45 minutes. If you go to the command prompt and issue a 'ping' command: ping lugerforum.com There are no replies from 72.71.199.44. This morning forum is available and a ping command to 72.71.199.44 shows the board is up. Mark

05-03-2016, 02:19 PM	#29
Edward Tinker Super Moderator Eternal Lifer LugerForum Patron Join Date: Jun 2002 Location: North of Spokane, WA Posts: 15,935 Thanks: 2,034 Thanked 4,533 Times in 2,093 Posts	Mark, I am surprised that John allows a ping. What seems consistent is that folks use www.lugerforum.com and fewer problems with forums.lugerForum.com Seems to me that folks should save the second one... . Also, I use Firefox and chrome....

05-03-2016, 11:08 PM	#33
cirelaw Lifer Lifetime Forum Patron Join Date: Dec 2003 Location: PORT ST LUCIE, FLORIDA Posts: 12,216 Thanks: 6,209 Thanked 4,133 Times in 2,173 Posts	I must admit having after having thousand posts, I have never noticed it down no more than a few times and each time I was given notice on the site! Thank You John and Ed for the privalege. Thank You all our Heros behind the scenes that makes my life even more enjoyable and for free!!!~~ Eric

05-04-2016, 09:15 AM	#34
markbritt User Join Date: Oct 2009 Location: NW Indiana Posts: 240 Thanks: 5 Thanked 48 Times in 22 Posts	Marc: While I agree with your statements on the name servers, I don't think this is the issue here. If you ping lugerforum.com, you should get a reply from 72.71.199.44. The local provider will resolve the lugerforum.com to 72.71.199.44. However, in this case, I pinged the server directly with 'ping 72.71.199.44' and there was no reply. There are no name server involved in this, so I do believe there is an intermittent issue with the hosting of lugerforum.com Mark

05-10-2016, 07:28 PM	#38
markbritt User Join Date: Oct 2009 Location: NW Indiana Posts: 240 Thanks: 5 Thanked 48 Times in 22 Posts	Guys: Hopefully this will assist in the troubleshooting. I am going to email these files to John S too. This morning at 6:30 am Central time I could not access the site. I attempted nslookup, ping and trace route commands and have the data. When I got home, I did the exact same steps when the site is up and running. It is not a DNS issue with local providers. It is not a routing issue. I suspect there is something with the server (perhaps a backup that is causing the NIC card not to respond? Ive seen this). LUGERFORUM DOWN: C:\Users\mark>nslookup lugerforum.com Server: UnKnown Address: 192.168.100.1 Non-authoritative answer: Name: lugerforum.com Address: 72.71.199.44 C:\Users\mark>tracert lugerforum.com Tracing route to lugerforum.com [72.71.199.44] over a maximum of 30 hops: 1 16 ms 18 ms 18 ms 66.11.108.1 2 20 ms 19 ms 18 ms 208-103-3-97.static.indianafiber.net [208.103.3.97] 3 18 ms 19 ms 19 ms 69-160-211-21.static.indianafiber.net [69.160.211.21] 4 26 ms 24 ms 24 ms te0-0-0-1.nr12.b021117-0.ind01.atlas.cogentco.com [38.104.214.101] 5 27 ms 23 ms 24 ms 154.24.38.29 6 39 ms 38 ms 38 ms be2721.rcr11.cvg02.atlas.cogentco.com [154.54.28.134] 7 36 ms 38 ms 38 ms be2729.rcr21.cmh02.atlas.cogentco.com [154.54.40.170] 8 36 ms 39 ms 38 ms be2732.ccr21.cle04.atlas.cogentco.com [154.54.40.250] 9 44 ms 43 ms 63 ms be2878.ccr21.alb02.atlas.cogentco.com [154.54.26.130] 10 48 ms 48 ms 49 ms 38.104.52.78 11 50 ms 54 ms 75 ms burl-lnk-70-109-168-139.ngn.east.myfairpoint.net[70.109.168.139] 12 54 ms 53 ms 54 ms fttp07-pos1-0.cncdnh.fast.myfairpoint.net [64.222.166.111] 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. C:\Users\mark>ping lugerforum.com Pinging lugerforum.com [72.71.199.44] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 72.71.199.44: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Users\mark>time The current time is: 6:33:57.99 Enter the new time: C:\Users\mark>date The current date is: Tue 05/10/2016 Enter the new date: (mm-dd-yy) LUGERFORUM UP: C:\Users\mark>nslookup lugerforum.com Server: UnKnown Address: 192.168.100.1 Non-authoritative answer: Name: lugerforum.com Address: 72.71.199.44 C:\Users\mark>tracert lugerforum.com Tracing route to lugerforum.com [72.71.199.44] over a maximum of 30 hops: 1 15 ms 15 ms 18 ms 66.11.108.1 2 23 ms 18 ms 18 ms 208-103-3-97.static.indianafiber.net [208.103.3.97] 3 24 ms 23 ms 24 ms 69-160-211-21.static.indianafiber.net [69.160.211.21] 4 27 ms 23 ms 24 ms te0-0-0-1.nr12.b021117-0.ind01.atlas.cogentco.com [38.104.214.101] 5 23 ms 24 ms 23 ms 154.24.38.29 6 38 ms 38 ms 39 ms be2721.rcr11.cvg02.atlas.cogentco.com [154.54.28.134] 7 39 ms 38 ms 38 ms be2729.rcr21.cmh02.atlas.cogentco.com [154.54.40.170] 8 35 ms 58 ms 34 ms be2732.ccr21.cle04.atlas.cogentco.com [154.54.40.250] 9 43 ms 44 ms 44 ms be2878.ccr21.alb02.atlas.cogentco.com [154.54.26.130] 10 48 ms 48 ms 49 ms 38.104.52.78 11 51 ms 48 ms 49 ms burl-lnk-70-109-168-128.ngn.east.myfairpoint.net[70.109.168.128] 12 54 ms 54 ms 54 ms burl-lnk-70-109-168-131.ngn.east.myfairpoint.net[70.109.168.131] 13 53 ms 50 ms 52 ms pool-64-222-213-128.port.east.myfairpoint.net [64.222.213.128] 14 58 ms 54 ms 59 ms pool-64-222-213-133.port.east.myfairpoint.net [64.222.213.133] 15 113 ms 118 ms 115 ms fttp07-pos0-0.cncdnh.fast.myfairpoint.net [64.222.166.71] 16 66 ms 61 ms 64 ms static-72-71-199-44.cncdnh.fast07.myfairpoint.net [72.71.199.44] Trace complete. C:\Users\mark>ping lugerforum.com Pinging lugerforum.com [72.71.199.44] with 32 bytes of data: Reply from 72.71.199.44: bytes=32 time=153ms TTL=115 Reply from 72.71.199.44: bytes=32 time=668ms TTL=115 Reply from 72.71.199.44: bytes=32 time=436ms TTL=115 Reply from 72.71.199.44: bytes=32 time=62ms TTL=115 Ping statistics for 72.71.199.44: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 62ms, Maximum = 668ms, Average = 329ms C:\Users\mark>

05-10-2016, 08:01 PM	#39
cirelaw Lifer Lifetime Forum Patron Join Date: Dec 2003 Location: PORT ST LUCIE, FLORIDA Posts: 12,216 Thanks: 6,209 Thanked 4,133 Times in 2,173 Posts	Thank You For All The Hard Work!!!