User Tools

Site Tools


technical_logs:harbourfront_centre

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
technical_logs:harbourfront_centre [2009/09/24 09:09]
gabe
technical_logs:harbourfront_centre [2013/09/28 16:06] (current)
Line 1: Line 1:
 +====== July 5, 2013 ======
 +As with the SLM network, I updated the Cloudtrax checkin URL. I could only (remotely) access the gateway router, though -- the other three are down.
 +
 +====== May 30, 2012 ======
 +Network monitoring enabled through Cloudtrax: [[http://​www.cloudtrax.com/​overview2.php?​id=wt-harb]]
 +
 +====== May 29, 2012 ======
 +Finally went down to investigate. Above the southeast corner of the gallery there'​s a spot where all the important wiring happens. There are two Ethernet switches there: one for a Harbourfront network, and one for Wireless Toronto. The WT switch had all the Ethernet removed. I plugged everything in, and the two orphaned routers were immediately back online.
 +
 +The router in the studio has weirdly long and eccentric ping times -- often indicative of wireless interference. I changed the channel from 6 to 11 and it *may* have helped things a little. This is something to investigate further. ​
 +
 +Also, there are a few routers on site with the ssid "​wtoronto."​ These appear to be routers installed by Harbourfront,​ but plugged into the Wireless Toronto network. (Not sure where; I didn't investigate.) No big deal, but worth noting. Presumably these are monitored by Harbourfront IT, which explains how they know so quickly whenever our network goes down. The only physical device I found was on the south patio (outside!).
 +
 +I've gotta go back in (remotely) and set up a monitoring cronjob on the routers.
 +
 +====== September 15, 2011 ======
 +A user emailed the support address describing trouble connecting. It sounded like our coverage area has shrunk. I checked, and I can't ping routers .67 or .68. (Was this ever resolved after March 28?) I emailed Juan to find out when I can go by to investigate.
 +
 +====== March 28, 2011 ======
 +I got an email from Harbourfront this morning saying that the network has been down since before 7. Weird, because wifidog reported it up. I checked the logs, and the wifidog checkins were consistent (every minute, exactly) and from the right IP address. I couldn'​t ping it via OpenVPN, though -- this is very weird. (OpenVPN is normally more resilient than the Wifidog gateway.)
 +
 +I saw the wirelesstoronto network, but didn't get a DHCP address. I forced a static IP, and could then ping 192.168.1.1. But I still couldn'​t SSH in (my attempts timed out -- maybe a sign of a high load on the box?).
 +
 +For fun, I tried pinging the other routers: .67, .68 and .69. Only .69 responded.
 +
 +I powercycled the gateway router (which is in the storage closet next to the Studio Theatre), and it came right back up. But I still can't ping router .67 and .68.
 +
 +====== July 23, 2010 ======
 +Wifidog reported that the router was down.  I was able to ssh in, and the same thing was happening as before -- the load was 0.00 (as reported by '​uptime'​),​ but 'wdctl status'​ didn't return anything in the 30 seconds I waited for it.  There were 10 entries in /​tmp/​dhcp.leases. ​ It seems to have lost its DNS servers again. ​ I added them to /​tmp/​resolv.conf,​ and also at the bottom of /​etc/​init.d/​S50dnsmasq,​ which is the script that creates /​tmp/​resolv.conf -- hopefully now it won't forget anymore?
 +
 +====== February 11, 2010 ======
 +Wifidog reported numerous 5-minute outages this morning, and Juan emailed saying that the system is down.  I connected to the main router, noticed that 'wdctl status'​ was taking a long time to run.  Just in case, I set static DNS servers in /​etc/​resolv.conf and nvram, and restarted wifidog. ​ Hopefully that fixes it.
 +
 ====== September 24, 2009 ====== ====== September 24, 2009 ======
 Juan from Harbourfront emailed to say that the network was down; Wifidog had been reporting that it was down for about 12 hours. ​ Gabe connected to the router via OpenVPN, noticed that the wifidog gateway had crashed, and restarted it.  The node is now checking into the auth server. Juan from Harbourfront emailed to say that the network was down; Wifidog had been reporting that it was down for about 12 hours. ​ Gabe connected to the router via OpenVPN, noticed that the wifidog gateway had crashed, and restarted it.  The node is now checking into the auth server.
technical_logs/harbourfront_centre.1253801398.txt.gz ยท Last modified: 2013/09/28 16:06 (external edit)