Flush your DNS

Post #390,049 by malraux 5/29/14 1:23:11 PM Reply	Flush your DNS It might be holding on to the old Linode address. Regards, -scott Welcome to Rivendell, Mr. Anderson.
Post #390,050 by Another Scott 5/29/14 1:34:18 PM Reply	Done (several times) Just closed Chrome, did "ipconfig /flushdns". Says it completed successfully. Restart Chrome, still 504 Gateway Timeout. I don't think it's being blocked (we typically get a warning page if something is blocked here). Weird... Thanks. Cheers, Scott.
Post #390,051 by folkert 5/29/14 2:03:55 PM 5/29/14 2:05:59 PM Reply	I'm getting weird routing... via AS6453... TATA Communications... No IP Addresses seems to have arpa-in-addr... May explain AS's issues. Ahhh ah, but then this just popped up: $ host 107.170.183.40 40.183.170.107.in-addr.arpa domain name pointer forum.iwethey.org. -- greg@gregfolkert.net "No snowflake in an avalanche ever feels responsible." --Stanislaw Jerzy Lec Edited by folkert May 29, 2014, 02:05:59 PM EDT Expand All History
Post #390,151 by Another Scott 5/30/14 7:11:07 PM Reply	Don't think that's it. Apparently packets are getting eaten at work. If I ran a GPL traceroute-type thingy (don't recall the name at the moment) I got output that indicated the IWeThey server was 3 hops and 1 msec away. That's obvisously not right... Of course, it could be that that was just a symptom, but it's clearly on my end. In the past, I've had to request that IWeThey not be blocked. I'll probably have to do that again at some point (if I get tired of using it on my phone ;-). FWIW. Thanks. Cheers, Scott.
Post #390,152 by folkert 5/30/14 8:31:20 PM Reply	Ok... The routing issues are spurious... sometimes BGP for that network gets a little spongy. -- greg@gregfolkert.net "No snowflake in an avalanche ever feels responsible." --Stanislaw Jerzy Lec
Post #390,254 by Another Scott 6/3/14 12:28:23 PM Reply	Spoke too soon. It's not being blocked at work. They're looking into it. Thanks. Cheers, Scott.
Post #391,731 by Another Scott 7/9/14 10:26:58 AM Reply	Woot! I'm back.
Post #391,750 by folkert 7/9/14 6:55:32 PM Reply	And the issue? -- greg@gregfolkert.net "No snowflake in an avalanche ever feels responsible." --Stanislaw Jerzy Lec
Post #391,751 by Another Scott 7/9/14 7:25:19 PM Reply	Dunno. Something upstream was blocking it.
Post #391,754 by folkert 7/9/14 7:34:20 PM Reply	Like I said... it looked like... a routing or peering issue to me. -- greg@gregfolkert.net "No snowflake in an avalanche ever feels responsible." --Stanislaw Jerzy Lec
Post #390,067 by Ashton 5/29/14 5:44:14 PM Reply	Ummm in OS X/Safari we don't gots the neat 'about:config' playground (presumably because Apple found cheaper labor after Steve ceased auditing?) But then, so-far I don't seem to have this problem anyway--moot?--thence no reply needed. ..Unless there IS an about:c option hidden somewhere; I'd like to find that sucker!
Post #390,076 by Another Scott 5/29/14 8:23:52 PM Reply	DNS cache is outside the browser. http://www.ihash.eu/2013/08/how-to-clear-dns-cache-in-mac-osx/ :-) There are various developer tools in Safari, but nothing obviously equivalent to "about:config". But that wouldn't help here. :-) HTH a bit. Cheers, Scott. (Who may be being too pedantic here. If so, sorry. :-)
Post #390,088 by Ashton 5/30/14 3:02:19 AM Reply	Not at all.. logic ain't pedantic; it's merely Accurate thus True (depending on your Truthiness-Table, right?) Thanks for tip; it's simple enough too (CL doesn't bother me ... until I have checked my syntax-thrice and then have to hit [Return]) (Love some of the comments in logs.. Goodnight Gracie ... Hate the ones that end--like the &^$##% fscking 5/28/14 4:32:18 PM c-50-185-182-41 [0x0-0x2b02b0].com.apple.Safari[4031] [0x0-0x2b02b0].com.apple.Safari 2014-05-28 16:32:18.214 PluginProcess[6086:903] __NSAutoreleaseNoPool(): Object 0x300140 of class NSCFDictionary autoreleased with no pool in place - just leaking [!!]** --which I seem to be able to confound by, merely Using a certain 'Dictionary' ... to look-up-in-Dictionary the definition of [any word-thing] and keeping that Open. (There may be neither rhyme nor Reason for that effect: but it Works. There may be n-'dictionaries' in there; it sure as hell ain't intuitively obvious) But humans improvise and so do I. Beats becoming really-competent.. in a way. (Time, for a Big-thing) We hangers-on at the periphery can absorb such stuff, until we're directed to something a lot like dirt snakes, say. :-0 (Haven't yet been Forced to do the Mavericks thing; real liff has interrupted that intent, so far.)
Post #390,092 by pwhysall 5/30/14 4:05:13 AM 5/30/14 4:10:12 AM Reply	Rule #1 of system log files Don't look at them unless you're trying to solve a specific problem Rule #2 Log lines almost always need to be taken in context Rule #3 They can be wrong, misleading, inaccurate or irrelevant, or all of the above Worked example: The "Dictionary" in your log line above isn't the kind of dictionary in which you look up the meanings of words. Well, it could be, but I'll bet a pint that it isn't. http://stackoverflow.com/questions/7156835/what-is-an-nscfdictionary https://developer.apple.com/library/ios/documentation/Cocoa/Reference/Foundation/Classes/NSDictionary_Class/Reference/Reference.html The general failure of the computing public to heed these rules is why those "remote support" phone scammers do so well. They get people to open the Event Viewer on Windows systems that are working perfectly satisfactorily, and of course it's full of things that are ERRORS and WARNINGS and OMGDEVILWORDS, so why yes I will give you my IP address and get you to log in remotely to "clean up" and bill me $200 for the privilege. The Console in OS X is no different. Edited by pwhysall May 30, 2014, 04:10:12 AM EDT Expand All History
Post #390,136 by Ashton 5/30/14 2:33:03 PM Reply	Thanks, Peter--illuminating. Have scanned both and see they are worth perusing until some grokking gels. Yes, I see that my 'fix' as does seem ~often to STOP the leaking stenographic-pool(?!) is not even a tame wild-goose chase. See that NSDictionary is a cascading class of (apparently multiply-useable?) procedures by a plethora of possible clients, nor Could one 'sleuth' from the stark form of any failure whose error-message involves 'leaking pools' (as can be only 'memory' disappearing--which Shouldn't be.) (I have blind-hopes that something~like 'about:config' shall inhabit the new-New Mavericks/Safari gussying-up..) Ex: When I command 'reopen last-session windows' I want it to load Only minimal stubs/or just links; NOT steal all that memory. I'd also like granularity re that reload command: like several categories maybe by date or name. (Hah..) I 'read' the log files periodically or natch, when there Is a glitch or seeming-one. I have taken your (and others') advice not-to imagine they are revealing [er, RAW] of much that a non-coder can use (this century anyway.. there was a time.. assembler.. CDC-6600.) As to letting ANYBODY (on a cold-call Fershure) into the Family Jewels, I judge that such folk must be those still stuck in, ..where's the 'any' key I'm supposed to strike? ie Before I'd allow remotes of any ilk deliberate access, I'd have to Know Them, their daughters ages' and hobbies and arrest records. If you're not paranoid, you'll be pwned in a trice, I comprehend. At least, though--one Can deduce via real English a few things by comparing 'normal' messages with Weird new ones--at times; at the least: OS X fixing-self? or blaming Safari specifically. This makes OS X a marvel of clarity compared with ..you know. Thanks again for another useful clarification.

Welcome to IWETHEY!