Skip to main content
Question

Jamf Pro 10.1 upgrade issues

  • December 19, 2017
  • 3 replies
  • 36 views

Forum|alt.badge.img+13

I upgraded my QA instance to Jamf Pro 10.1 today.

On a new machine, I tried to launch Imaging and I'm getting the following error when launching Jamf Imaging:

On an existing machine, it downloaded the new binary and upgraded Self Service, but has been hung executing a script all afternoon. In the console, it's just looping through the following:

Mon Dec 18 19:53:33 MYMACNAME jamf[1216]: Daemon starting Mon Dec 18 19:53:33 MYMACNAME jamf[1216]: The download of /Library/Application Support/JAMF/tmp/JamfBundle.tar.gz failed. Mon Dec 18 19:53:34 MYMACNAME jamf[1216]: Informing the JSS about login for user LOCALUSER Mon Dec 18 20:11:55 MYMACNAME jamf[4052]: Checking for policies triggered by "recurring check-in" for user "LOCALUSER"... Mon Dec 18 20:11:57 MYMACNAME jamf[4052]: Could not connect to the JSS. Looking for cached policies... Mon Dec 18 20:11:58 MYMACNAME jamf[4052]: Adding launchd task com.jamfsoftware.task.checkForTasks... Mon Dec 18 20:12:00 MYMACNAME jamf[4217]: An Error Occurred while attempting to manage the computer: Connection failure: "The Internet connection appears to be offline." Mon Dec 18 20:12:00 MYMACNAME jamf[4217]: Enforcing scheduled tasks... Mon Dec 18 20:12:00 MYMACNAME jamf[4217]: Removing existing launchd task /Library/LaunchDaemons/com.jamfsoftware.task.1.plist... Mon Dec 18 20:12:01 MYMACNAME jamf[4217]: Adding launchd task com.jamfsoftware.task.1... Mon Dec 18 20:12:01 MYMACNAME jamf[1216]: Daemon shutdown completed Mon Dec 18 20:12:01 MYMACNAME jamf[1216]: Daemon exiting Mon Dec 18 20:12:01 MYMACNAME jamf[4217]: Removing existing launchd task /Library/LaunchDaemons/com.jamfsoftware.jamf.daemon.plist... Mon Dec 18 20:12:01 MYMACNAME jamf[4217]: Creating launch daemon... Mon Dec 18 20:12:01 MYMACNAME jamf[4217]: Creating launch agent... Mon Dec 18 20:12:01 MYMACNAME jamf[4217]: The management framework will be enforced as soon as all policies are done executing. Mon Dec 18 20:12:01 MYMACNAME jamf[4265]: Informing the JSS about login for user LOCALUSER Mon Dec 18 20:12:02 MYMACNAME jamf[4265]: Daemon starting Mon Dec 18 20:12:02 MYMACNAME jamf[4265]: The download of /Library/Application Support/JAMF/tmp/JamfBundle.tar.gz failed. Mon Dec 18 20:12:03 MYMACNAME jamf[4265]: Informing the JSS about login for user LOCALUSER

These are both on our internal network and have no problem accessing the JSS directly in Chrome.

I've opened a case as well, just wanted to throw it out there in case anyone else has seen this.

3 replies

Forum|alt.badge.img+2
  • New Contributor
  • December 19, 2017

Just adding my comments to stay in loop on this thread. Thanks


ImAMacGuy
Forum|alt.badge.img+23
  • Esteemed Contributor
  • December 19, 2017

10.1 was removed from the upgrades because of some bugs...

Jamf notification


emily
Forum|alt.badge.img+26
  • Hall of Fame
  • December 19, 2017

Looks like you might have a 10.1.1 to try and see if it works any better…