{"id":2998,"date":"2013-02-15T09:39:19","date_gmt":"2013-02-15T14:39:19","guid":{"rendered":"http:\/\/chriscolotti.us\/?p=2998"},"modified":"2014-08-22T14:06:53","modified_gmt":"2014-08-22T18:06:53","slug":"workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table","status":"publish","type":"post","link":"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/","title":{"rendered":"Workaround for vSphere 5.1 Guest Unable to collect IPv4 routing table"},"content":{"rendered":"<p>Folks this has become an interesting discussion on a VMware Community Forum as of a few weeks ago about this vSphere 5.1 error. \u00a0In fact I myself ran into the same issue on a new build with the vCloud Service Evaluation cloud a couple of weeks ago. \u00a0I decided being a good\u00a0citizen\u00a0and VMware employee to start an internal discussion of this to see where it could lead. \u00a0Below is a screen show you MIGHT see showing the error, however what I can tell you now is this error actually has NOTHING to do with the root cause issue so let me explain.<\/p>\n<p style=\"text-align: center;\"><a href=\"http:\/\/chriscolotti.us\/wp-content\/uploads\/2013\/02\/vmsvct.png\"><img loading=\"lazy\" decoding=\"async\" data-attachment-id=\"3000\" data-permalink=\"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/attachment\/vmsvct\/\" data-orig-file=\"https:\/\/chriscolotti.us\/wp-content\/uploads\/2013\/02\/vmsvct.png\" data-orig-size=\"758,419\" data-comments-opened=\"1\" data-image-meta=\"{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;}\" data-image-title=\"vmsvct\" data-image-description=\"\" data-image-caption=\"\" data-medium-file=\"https:\/\/chriscolotti.us\/wp-content\/uploads\/2013\/02\/vmsvct-300x165.png\" data-large-file=\"https:\/\/chriscolotti.us\/wp-content\/uploads\/2013\/02\/vmsvct.png\" class=\"aligncenter  wp-image-3000\" alt=\"vSphere\" src=\"http:\/\/chriscolotti.us\/wp-content\/uploads\/2013\/02\/vmsvct.png\" width=\"455\" height=\"251\" srcset=\"https:\/\/chriscolotti.us\/wp-content\/uploads\/2013\/02\/vmsvct.png 758w, https:\/\/chriscolotti.us\/wp-content\/uploads\/2013\/02\/vmsvct-300x165.png 300w\" sizes=\"(max-width: 455px) 100vw, 455px\" \/><\/a><\/p>\n<h3 style=\"text-align: left;\">The vSphere Setup To Reproduce:<\/h3>\n<ol>\n<li><span style=\"line-height: 12.796875px;\">vSphere 5.1 and\/or vCloud Director<\/span><\/li>\n<li>CentOS 6.3 Guest (although other versions also seem to hang)<\/li>\n<li>Tools installed post OS installation<\/li>\n<li>Wait about 10-15 minutes<\/li>\n<li>Reboot the Guest Virtual Machine<\/li>\n<\/ol>\n<p style=\"text-align: left;\">This is rather easy and is something anyone can do. \u00a0What I can say for sure, this is not tools version related, it is not even virtual hardware related, it is something with the tools and vSphere 5.1 specifically, regardless of versions. \u00a0I actually tested both:<\/p>\n<ul>\n<li><span style=\"line-height: 12.796875px;\">HW8 and Tools Version 8\u00a0running on vSphere 5.1<\/span><\/li>\n<li>HW9 and Tools Version 9 running on vSphere 5.1<\/li>\n<li>Uninstalled the tools and things work fine<\/li>\n<\/ul>\n<p style=\"text-align: left;\">The error itself is arbitrary and happens to be presented while the Virtual Machine is simply trying to finish the boot. \u00a0I know this as I was asked to start renaming certain libraries\u00a0including\u00a0libguestinfo.so which removed the error in the screen, but the Virtual Machine still stalls on boot. \u00a0This error is completely un-related to the underlying root cause which is actually that the Virtual Machine is hanging on boot for about 10-15 minutes.<\/p>\n<h3 style=\"text-align: left;\">The Real Problem<\/h3>\n<p>So in the spirit of troubleshooting, engineering used my test Virtual Machines to go through other libraries until we isolated the libtimeSync.so library. \u00a0Now, if you recall way back early in vCloud Director I ran into a <a href=\"http:\/\/chriscolotti.us\/vmware\/gotcha-the-importance-of-ntp-to-vmware-vcloud-director\/\" target=\"_blank\">time sync issue<\/a> that was ultimately being caused by the fact NTP was not enabled on a cell. \u00a0However, what I pointed out in that article was that EVERY virtual machine,\u00a0regardless\u00a0if the tools are set to sync with the host or not when the tools running will ALWAYS time sync initially on boot if the tools are installed. \u00a0Then once the tools are running, the settings of sync with host or not are enforced.<\/p>\n<p>What appears to be happening here and we don&#8217;t yet have the &#8220;why&#8221; is that the time sync library is causing the hang on the initial boot. \u00a0So now that we know the reason it is hanging and the library causing it we can do a quick work around which for most people should be good until we can get a final root cause as to the reason the library is just taking so long.<\/p>\n<h3>The vSphere Workaround<\/h3>\n<p>This is so simple you are going to wonder why I made you read the rest of the article. \u00a0Well, frankly I think it&#8217;s important to understand the troubleshooting we have taken to understand and isolate the issue so you know why it&#8217;s happening not just the &#8220;fix&#8221;. \u00a0So what that the answer right now seems to be simple assuming you only have access to the vSphere guest itself like I do in a fully hosted environment:<\/p>\n<ul>\n<li><span style=\"line-height: 12.796875px;\"><span style=\"line-height: 12.796875px;\">Rename libtimeSync.so to\u00a0libtimeSync.so.bak (or something else you choose)<\/span><\/span><\/li>\n<li>There is a <a href=\"http:\/\/kb.vmware.com\/kb\/1189\" target=\"_blank\">KB Article<\/a> that you might want to read and see it you can try that as well if you have access to the full back end<\/li>\n<\/ul>\n<p>The File locations are as follows:<\/p>\n<p>\/usr\/lib\/vmware-tools\/plugins32\/vmsvc\/libtimeSync.so<br \/>\n\/usr\/lib\/vmware-tools\/plugins64\/vmsvc\/libtimeSync.so<\/p>\n<p>Since most of you using Linux are most likely using NTP, this shouldn&#8217;t interfere with the overall time sync of your guest, as NTP should start-up soon after and do it&#8217;s sync and you should be good to go for now until a more long-term explanation and fix is put forth. \u00a0This should get you by and allow you to keep the tools installed without the warm reboot hanging issue.<\/p>\n<p>I hope this helps, and always troubleshooting is an ongoing effort fo trial and error. \u00a0Thanks to the vCloud Service Evaluation setup for providing a fast easy way to re-produce AND provide access to others to help continue to troubleshoot this problem. \u00a0If this was only in my lab if would have been much harder to provide the access.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Folks this has become an interesting discussion on a VMware Community Forum as of a few weeks ago about this vSphere 5.1 error. \u00a0In fact I myself ran into the same issue on a new build with the vCloud Service Evaluation cloud a couple of weeks ago. \u00a0I decided being a good\u00a0citizen\u00a0and VMware employee to &hellip;<\/p>\n","protected":false},"author":2,"featured_media":710,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"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","enabled":false}}},"categories":[19,9,12],"tags":[247,381],"jetpack_publicize_connections":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v22.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Workaround: vSphere 5.1 Guest Unable to collect IPv4 routing table<\/title>\n<meta name=\"description\" content=\"Some people have run into this vSphere 5.1 issue with the error Guest Unable to collect IPv4 routing table. I&#039;ve worked internally to get a work around.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Workaround: vSphere 5.1 Guest Unable to collect IPv4 routing table\" \/>\n<meta property=\"og:description\" content=\"Some people have run into this vSphere 5.1 issue with the error Guest Unable to collect IPv4 routing table. I&#039;ve worked internally to get a work around.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/\" \/>\n<meta property=\"og:site_name\" content=\"Chris Colotti&#039;s Blog\" \/>\n<meta property=\"article:published_time\" content=\"2013-02-15T14:39:19+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2014-08-22T18:06:53+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/i0.wp.com\/chriscolotti.us\/wp-content\/uploads\/2011\/09\/gotcha1.jpeg?fit=160%2C160&ssl=1\" \/>\n\t<meta property=\"og:image:width\" content=\"160\" \/>\n\t<meta property=\"og:image:height\" content=\"160\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Chris Colotti\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@ccolotti\" \/>\n<meta name=\"twitter:site\" content=\"@ccolotti\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Chris Colotti\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/\",\"url\":\"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/\",\"name\":\"Workaround: vSphere 5.1 Guest Unable to collect IPv4 routing table\",\"isPartOf\":{\"@id\":\"https:\/\/chriscolotti.us\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/chriscolotti.us\/wp-content\/uploads\/2011\/09\/gotcha1.jpeg\",\"datePublished\":\"2013-02-15T14:39:19+00:00\",\"dateModified\":\"2014-08-22T18:06:53+00:00\",\"author\":{\"@id\":\"https:\/\/chriscolotti.us\/#\/schema\/person\/7dd10fd3d400b31cbb9a4a4a14adb0c7\"},\"description\":\"Some people have run into this vSphere 5.1 issue with the error Guest Unable to collect IPv4 routing table. I've worked internally to get a work around.\",\"breadcrumb\":{\"@id\":\"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/#primaryimage\",\"url\":\"https:\/\/chriscolotti.us\/wp-content\/uploads\/2011\/09\/gotcha1.jpeg\",\"contentUrl\":\"https:\/\/chriscolotti.us\/wp-content\/uploads\/2011\/09\/gotcha1.jpeg\",\"width\":\"160\",\"height\":\"160\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/chriscolotti.us\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Workaround for vSphere 5.1 Guest Unable to collect IPv4 routing table\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/chriscolotti.us\/#website\",\"url\":\"https:\/\/chriscolotti.us\/\",\"name\":\"Chris Colotti&#039;s Blog\",\"description\":\"Thoughts and Theories About...\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/chriscolotti.us\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/chriscolotti.us\/#\/schema\/person\/7dd10fd3d400b31cbb9a4a4a14adb0c7\",\"name\":\"Chris Colotti\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/chriscolotti.us\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/c93553a4a3e76f774ead33ebad5dbc1e?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/c93553a4a3e76f774ead33ebad5dbc1e?s=96&d=mm&r=g\",\"caption\":\"Chris Colotti\"},\"description\":\"Chris is active on the VMUG and event speaking circuit and is available for many events if you want to reach out and ask. Previously to this he spent close to a decade working for VMware as a Principal Architect. Previous to his nine plus years at VMware, Chris was a System Administrator that evolved his career into a data center architect. Chris spends a lot of time mentoring co-workers and friends on the benefits of personal growth and professional development. Chris is also amongst the first VMware Certified Design Experts (VCDX#37), and author of multiple white papers. In his spare time he helps his wife Julie run her promotional products as the accountant, book keeper, and IT Support. Chris also believes in both a healthy body and healthy mind, and has become heavily involved with fitness as a Diamond Team Beachbody Coach using P90X and other Beachbody Programs. Although Technology is his day job, Chris is passionate about fitness after losing 60 pounds himself in the last few years.\",\"sameAs\":[\"http:\/\/chriscolotti.us\"],\"url\":\"https:\/\/chriscolotti.us\/author\/ccolotti\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Workaround: vSphere 5.1 Guest Unable to collect IPv4 routing table","description":"Some people have run into this vSphere 5.1 issue with the error Guest Unable to collect IPv4 routing table. I've worked internally to get a work around.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/","og_locale":"en_US","og_type":"article","og_title":"Workaround: vSphere 5.1 Guest Unable to collect IPv4 routing table","og_description":"Some people have run into this vSphere 5.1 issue with the error Guest Unable to collect IPv4 routing table. I've worked internally to get a work around.","og_url":"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/","og_site_name":"Chris Colotti&#039;s Blog","article_published_time":"2013-02-15T14:39:19+00:00","article_modified_time":"2014-08-22T18:06:53+00:00","og_image":[{"width":"160","height":"160","url":"https:\/\/i0.wp.com\/chriscolotti.us\/wp-content\/uploads\/2011\/09\/gotcha1.jpeg?fit=160%2C160&ssl=1","type":"image\/jpeg"}],"author":"Chris Colotti","twitter_card":"summary_large_image","twitter_creator":"@ccolotti","twitter_site":"@ccolotti","twitter_misc":{"Written by":"Chris Colotti","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/","url":"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/","name":"Workaround: vSphere 5.1 Guest Unable to collect IPv4 routing table","isPartOf":{"@id":"https:\/\/chriscolotti.us\/#website"},"primaryImageOfPage":{"@id":"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/#primaryimage"},"image":{"@id":"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/#primaryimage"},"thumbnailUrl":"https:\/\/chriscolotti.us\/wp-content\/uploads\/2011\/09\/gotcha1.jpeg","datePublished":"2013-02-15T14:39:19+00:00","dateModified":"2014-08-22T18:06:53+00:00","author":{"@id":"https:\/\/chriscolotti.us\/#\/schema\/person\/7dd10fd3d400b31cbb9a4a4a14adb0c7"},"description":"Some people have run into this vSphere 5.1 issue with the error Guest Unable to collect IPv4 routing table. I've worked internally to get a work around.","breadcrumb":{"@id":"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/#primaryimage","url":"https:\/\/chriscolotti.us\/wp-content\/uploads\/2011\/09\/gotcha1.jpeg","contentUrl":"https:\/\/chriscolotti.us\/wp-content\/uploads\/2011\/09\/gotcha1.jpeg","width":"160","height":"160"},{"@type":"BreadcrumbList","@id":"https:\/\/chriscolotti.us\/vmware\/workaround-for-vsphere-5-1-guest-unable-to-collect-ipv4-routing-table\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/chriscolotti.us\/"},{"@type":"ListItem","position":2,"name":"Workaround for vSphere 5.1 Guest Unable to collect IPv4 routing table"}]},{"@type":"WebSite","@id":"https:\/\/chriscolotti.us\/#website","url":"https:\/\/chriscolotti.us\/","name":"Chris Colotti&#039;s Blog","description":"Thoughts and Theories About...","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/chriscolotti.us\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/chriscolotti.us\/#\/schema\/person\/7dd10fd3d400b31cbb9a4a4a14adb0c7","name":"Chris Colotti","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/chriscolotti.us\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/c93553a4a3e76f774ead33ebad5dbc1e?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/c93553a4a3e76f774ead33ebad5dbc1e?s=96&d=mm&r=g","caption":"Chris Colotti"},"description":"Chris is active on the VMUG and event speaking circuit and is available for many events if you want to reach out and ask. Previously to this he spent close to a decade working for VMware as a Principal Architect. Previous to his nine plus years at VMware, Chris was a System Administrator that evolved his career into a data center architect. Chris spends a lot of time mentoring co-workers and friends on the benefits of personal growth and professional development. Chris is also amongst the first VMware Certified Design Experts (VCDX#37), and author of multiple white papers. In his spare time he helps his wife Julie run her promotional products as the accountant, book keeper, and IT Support. Chris also believes in both a healthy body and healthy mind, and has become heavily involved with fitness as a Diamond Team Beachbody Coach using P90X and other Beachbody Programs. Although Technology is his day job, Chris is passionate about fitness after losing 60 pounds himself in the last few years.","sameAs":["http:\/\/chriscolotti.us"],"url":"https:\/\/chriscolotti.us\/author\/ccolotti\/"}]}},"jetpack_featured_media_url":"https:\/\/chriscolotti.us\/wp-content\/uploads\/2011\/09\/gotcha1.jpeg","jetpack_shortlink":"https:\/\/wp.me\/p1K3dw-Mm","jetpack_sharing_enabled":true,"jetpack_likes_enabled":false,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/chriscolotti.us\/wp-json\/wp\/v2\/posts\/2998"}],"collection":[{"href":"https:\/\/chriscolotti.us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/chriscolotti.us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/chriscolotti.us\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/chriscolotti.us\/wp-json\/wp\/v2\/comments?post=2998"}],"version-history":[{"count":0,"href":"https:\/\/chriscolotti.us\/wp-json\/wp\/v2\/posts\/2998\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/chriscolotti.us\/wp-json\/wp\/v2\/media\/710"}],"wp:attachment":[{"href":"https:\/\/chriscolotti.us\/wp-json\/wp\/v2\/media?parent=2998"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/chriscolotti.us\/wp-json\/wp\/v2\/categories?post=2998"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/chriscolotti.us\/wp-json\/wp\/v2\/tags?post=2998"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}