{"id":5365,"date":"2014-12-01T18:03:36","date_gmt":"2014-12-01T08:03:36","guid":{"rendered":"http:\/\/nsrd.info\/blog\/?p=5365"},"modified":"2018-12-11T13:38:10","modified_gmt":"2018-12-11T03:38:10","slug":"a-locale-problem","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2014\/12\/01\/a-locale-problem\/","title":{"rendered":"A locale problem"},"content":{"rendered":"<p>I had a doozy of a problem a short while ago \u2013 NetWorker 8.2 in a big environment, and every now and&nbsp;then the NMC Recovery interface would behave oddly. By oddly:<\/p>\n<ul>\n<li>Forward\/Back buttons&nbsp;might stop working when choosing&nbsp;between specific backups in the file browser<\/li>\n<li>Manually entering a date\/time might jump you to a&nbsp;different date\/time<\/li>\n<li>Backups that were executed extremely closely to each other (e.g., &lt;15 minutes apart) might take&nbsp;a while to show up in NMC<\/li>\n<\/ul>\n<p>Oddly enough, it&nbsp;<em>actually<\/em> looked like a DNS issue in the environment. Windows nslookups could often timeout for 2 x 2 seconds before returning successfully, and just occasionally the&nbsp;gstd.raw log file on the NMC server would report&nbsp;name resolution oddities. This seemed borne out by the fact that&nbsp;recoveries executed directly from clients using the old winworkr interface or the CLI would work \u2013 with a separate NMC and NetWorker server, the name resolution path between the types of recoveries were guaranteed to be different.<\/p>\n<hr>\n<p><em>(Just a quick interrupt. The NetWorker Usage Survey is happening again. Every year I ask readers to participate and tell me a bit about their environment. It&#8217;s short \u2013 I promise! \u2013 you only need around 5 minutes to&nbsp;answer the questions. When you&#8217;re&nbsp;finished reading this article, I&#8217;d really appreciate if you could <a title=\"NetWorker Usage Survey\" href=\"https:\/\/nsrd.info\/blog\/2014\/11\/30\/networker-usage-survey-2014-2015\/\" target=\"_blank\">jump over and do the survey<\/a>.)&nbsp;<\/em><\/p>\n<hr>\n<p>But it was an interesting one. Over the years I&#8217;ve seen a few oddities in the way NMC behaves, and I wasn&#8217;t inclined to completely let NMC off the hook. So while we were digging down on the DNS scenarios, I was also talking to the support and eventually&nbsp;engineering teams&nbsp;about it from an NMC perspective.<\/p>\n<p>It turned out to be a locale problem. A very locale problem. It&nbsp;also eventually made sense why I couldn&#8217;t reproduce it in a lab. You see, I&#8217;m a bit of a lazy Windows system builder \u2013 I do the install, patch it and then get down to work. I certainly don&#8217;t do customisation of the languages on the&nbsp;systems or anything like that.<\/p>\n<p>But the friendly engineer assigned to the case&nbsp;<em>did<\/em> do just that, and it became obvious that the problems were only reproducible when the&nbsp;the regional display formats on a Windows host were set to either &#8220;English (Australian)&#8221; or &#8220;English (New Zeaaland)&#8221;.<\/p>\n<p>By Windows&nbsp;<em>host<\/em>, I mean the machine that&nbsp;the NMC Java application was being run on \u2013 not the NMC server, not the NetWorker server, but the NMC&nbsp;<em>client<\/em>.<\/p>\n<p>So, the following would&nbsp;allow NMC to behave oddly:<\/p>\n<p><a href=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2014\/12\/english-AU.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-5366\" src=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2014\/12\/english-AU.png\" alt=\"english-AU\" width=\"505\" height=\"600\" srcset=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2014\/12\/english-AU.png 801w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2014\/12\/english-AU-252x300.png 252w\" sizes=\"auto, (max-width: 505px) 100vw, 505px\" \/><\/a><\/p>\n<p>But,&nbsp;with&nbsp;the following&nbsp;setting, the NMC recovery&nbsp;interface would purr like a&nbsp;kitten:<\/p>\n<p><a href=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2014\/12\/english-US.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-5367\" src=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2014\/12\/english-US.png\" alt=\"english-US\" width=\"506\" height=\"600\" srcset=\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2014\/12\/english-US.png 803w, https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2014\/12\/english-US-252x300.png 252w\" sizes=\"auto, (max-width: 506px) 100vw, 506px\" \/><\/a><\/p>\n<p>It&#8217;s&nbsp;certainly something worth keeping in mind if you&#8217;re&nbsp;using the recovery interface in NMC a lot \u2013 if something looks like it&#8217;s not quite right,&nbsp;flick your regional formats setting across to &#8220;English (United States)&#8221; and see whether that makes a big difference.<\/p>\n<hr>\n<p><em>(Hey, now you&#8217;ve finished reading this article, just a friendly reminder:&nbsp;The NetWorker Usage Survey is happening again. Every year I ask readers to participate and tell me a bit about their environment. It&#8217;s short \u2013 I promise! \u2013 you only need around 5 minutes to&nbsp;answer the questions. When you&#8217;re&nbsp;finished reading this article, I&#8217;d really appreciate if you could&nbsp;<a title=\"NetWorker Usage Survey\" href=\"https:\/\/nsrd.info\/blog\/2014\/11\/30\/networker-usage-survey-2014-2015\/\" target=\"_blank\">jump over and do the survey<\/a>.)<\/em><\/p>\n<hr>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I had a doozy of a problem a short while ago \u2013 NetWorker 8.2 in a big environment, and every&hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[19],"tags":[419,633,638,788,1252],"class_list":["post-5365","post","type-post","status-publish","format-standard","hentry","category-recovery","tag-gui","tag-networker-management-console","tag-nmc","tag-recover","tag-recovery"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pKpIN-1ox","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/5365","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/comments?post=5365"}],"version-history":[{"count":6,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/5365\/revisions"}],"predecessor-version":[{"id":7446,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/posts\/5365\/revisions\/7446"}],"wp:attachment":[{"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/media?parent=5365"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/categories?post=5365"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nsrd.info\/blog\/wp-json\/wp\/v2\/tags?post=5365"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}