08:32:40,369 INFO c.j.j.l.LpsServerSocketListener Sleeping for 5000 ms before retry of server socket bind for address /109.171.129.139:8389 Oct 09 08:18:04 lthjamf systemd: Started LSB: JAMF Infrastructure Manager. Oct 09 08:18:04 lthjamf systemd: Starting LSB: JAMF Infrastructure Manager. └─13460 /usr/bin/java =/etc/jamf-im nfigurationFile=/etc/jamf-im/jsam/logging/log4j2-jamf-im-launcher.xml -DjsamLogPath=/var/log -jar jsam-launcher-1.3.0.jar Loaded: loaded (/etc/init.d/jamf-im bad vendor preset: enabled)Īctive: active (running) since Mon 08:18:04 AST 9min ago rvice - LSB: JAMF Infrastructure Manager.Thanks for your responses, when I tried nc -z 8389 from outside my network it seemed to just time out with no error message or any message of any kind. Then restart the JIM/LDAP Proxy service and that startup error will be gone. Or, just edit /etc/hosts and add a line for the enrolled hostname so it never even has to ask DNS. The solution is to have split-scope DNS (Jamf Cloud resolves to the external IP address, the JIM resolves to it's own internal IP address. 14:43:21,839 ERROR c.j.j.l.LpsServerSocketListener Failed to obtain server socket for address /13.93.87.150:31337Ĭom.: Failed to bind server socket to Īt .(LpsSocketSupplier.java:136) ~ If this is not right, you will see the below in the JIM logs because there's no network adaptor on the JIM server that has that external IP address. That needs to be the internal IP address on the JIM host, not the external IP address that Jamf Cloud will be contacting. It will show the IP address that it gets back when it tries to resolve "". on the JIM itself, ping the JIM's enrolled hostname (e.g.
Not enough information here to say if this is your problem, but here's one common gotcha that trips people up.
0 kommentar(er)
