portal entry

Are you putting the secret key (shown in the Dev svr cf admin pmt settings page) into the pmt pointing to it?

Comment by Charlie Arehart

yup definitely have the secret key entered. I think possibly what I'm missing is allow traffic on port 9250 from monitored node to PMT ES instance.  waiting for IT to verify that's what's needed.    the setup guides seems to assume that PMT and monitored node can always communicate

Comment by yuliangr39032863

interesting too....apparently the secret key is attached to the license somehow.  i just applied our enterprise license to the dev server and the secret key changed.

Comment by yuliangr39032863

Interesting stuff. Do keep us posted. :)

Comment by Charlie Arehart

I had IT open the firewall from dev server to my workstation port 9250.   retried the PMT connection.   it thinks for a bit longer and then returns hard error.    I'm installing wireshark to see who is actually throwing this error, the pmt or the monitored node. <h1>HTTP Status 500 – Internal Server Error</h1> <hr /> Type Exception Report Description The server encountered an unexpected condition that prevented it from fulfilling the request. Exception java.lang.NullPointerException com.fasterxml.jackson.core.JsonFactory.createParser(JsonFactory.java:879) com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2842) coldfusion.monitor.es.JSONConverter.toMonitorSettings(JSONConverter.java:164) coldfusion.monitor.es.Configuration.getMonitorSettings(Configuration.java:482) coldfusion.monitor.es.Configuration.initializeSettings(Configuration.java:388) coldfusion.monitor.MonitoringServiceImpl.initialize(MonitoringServiceImpl.java:662) coldfusion.monitor.MonitoringServiceImpl.store(MonitoringServiceImpl.java:722) coldfusion.monitor.MonitoringServiceImpl.intializeNodeWithEs(MonitoringServiceImpl.java:501) coldfusion.monitor.PMSGenericServlet.doPost(PMSGenericServlet.java:194) javax.servlet.http.HttpServlet.service(HttpServlet.java:660) javax.servlet.http.HttpServlet.service(HttpServlet.java:741) coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:311) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) Note The full stack trace of the root cause is available in the server logs. <hr /> <h3>Apache Tomcat/9.0.10</h3>

Comment by yuliangr39032863

That's an odd one. Use of the pmt seems low, judging from community feedback here, so I'm not aware of that error or it's cause, or even best steps to diagnose. If you don't solve it, email the folks at cfinstal@adobe.com, as it's about setup. And I hope you'll report back with the resolution, so all can learn.

Comment by Charlie Arehart

I'm having exact same issue; main CF instance + PMT works fine, but it won't let me manually add a second server without the same error message (except mine says localhost, 9250 - and there IS something running locally on 9250, this ElasticSearch thingy I imagine). But there isn't anything running on port 9250 of the "other" server to be monitored, so opening that port won't have any effect.  The error message appears to be extremely misleading.  The interface for adding/changing the servers to be monitored doesn't look very promising either, e.g. there's not even a way to delete a server once you've tried adding it - you can only enable/disable it !

Comment by AndyLorenz

Andy, there is indeed a lot about the PMT that can be hard to setup, as there are so many moving parts--and all the more when the PMT and (its datastore) are on separate machines from the server(s) to be monitored. Yes, of course, that's how it's DESIGNED to work. I'm just saying that people do struggle when some aspect of configuration doesn't work. There are multiple diagnostics to consider, as well as multiple configuration options to possibly tweak. Too many to easily propose what to do next. And as I reported to the op (yuliangr), that complication may call for reaching out to Adobe directly to get their help, at cfinstal@adobe.com. There's just no guarantee they will see these discussions here.

Comment by Charlie Arehart

Hi, For the first issue which you are mentioning, please copy the secret from Dev server admin's PMT page and copy it while registering it with PMT as suggested by Charlie. For the second issue it seems like your second instance is not able to communicate to ElasticSearch of PMT  at host: DEV-YR and port:9,250. For further support please reach out to cfinstal@adobe.com or please share your mail id we will setup a screen share session. Thanks, Mayur Jain

Comment by MayurCF

<p>Mayur, thanks for jumping in. As for your second point, is it really so that the CF instance being MONITORED needs to reach the datastore? I’ve assumed (as many may) that it would be the PMT only which talks to the datastore, having pulled metrics from the CF instance. Can you clarify?</p>

Comment by Charlie Arehart

<p>Hi Charlie,</p><p>Actually Every CFinstance pushes the date to the datastore. On registering a CF node with PMT. PMT shares the datastore details with CF node, which is then used by CF to push metric data to datastore. PMT can talk to individual CF nodes for active request monitoring, thread and heapdump.</p><p>Thanks,</p><p>Mayur Jain</p>

Comment by MayurCF

Got it. Thanks. Is there any page (in docs or a blog post) that depicts that route of communication among the 3 components (instance, pmt, datastore), to help folks anticipate/confirm successful communication when things are not workimg? Sorry if I've missed or forgotten it.

Comment by Charlie Arehart