Skip to main content
Question

Problem with JSS

  • December 20, 2011
  • 2 replies
  • 10 views
J
Forum|alt.badge.img+3

Hello, i'm new here and currently running the trial of Casper, but
right now I'm bashing my head against a wall out of frustration. What
I'm seeing is that inventory doesn't seem to update properly, i'm
using 8.31.

Here's what I get when running jamf recon on a machine via ssh.
-----
hjl$ sudo jamf recon -realname "Jurgen Linde" -displayJSSTraffic
Retrieving Inventory Preferences from https://jssname:8443//... Uploaded: 640 bytes Downloaded: 1 KB Total Traffic: 2 KB

Locating Hard Drive Information...
Locating Hardware Information (Mac OS X 10.7.2)...
Locating Applications...
Locating Fonts...
Executing Unix Applications...
Locating Receipts...
Gathering Application Usage Information...
Finding Extension Attributes...
Submitting data to https://jssname:8443//... Uploaded: 147 KB Downloaded: 0 bytes Total Traffic: 147 KB

There was an error submitting the computer to the JSS. Here is what
the JSS reported back:

<request>650</request><uploaded>150845</uploaded><downloaded>0</downloaded>
-----

Running this command...
-----
hjl$ sudo jamf recon -realname "Jurgen Linde"
Password:
Retrieving Inventory Preferences from
https://02cpt-xodm01.za.ds.naspers.com:8443//...
Locating Hard Drive Information...
Locating Hardware Information (Mac OS X 10.7.2)...
Locating Applications...
Locating Fonts...
Executing Unix Applications...
Locating Receipts...
Gathering Application Usage Information...
Finding Extension Attributes...
Submitting data to https://02cpt-xodm01.za.ds.naspers.com:8443//...
-----

So when adding the DisplayJSSTraffic flag, I can see that there's an
obvious problem...when the flag is not there, it appears as if it runs
fine, but obviously it doesn't. What I also see in the particular
computer's log on the JSS is that zero entry appears on the inventory
log, I can run this command manually as many times as I want, it just
doesn't show up, as if it never ran an inventory.

It really doesn't make sense at all because when I run Recon.app it
does work 100%.

The fact that the recon command causes all scripts to fail that
interact with it. Just driving me a little insane right now ;)

Any ideas?! I'm using the default self-signed cert btw.

    2 replies

    S
    Forum|alt.badge.img+12
    • sean
    • Contributor
    • December 20, 2011

    Jurgen,

    Try running:

    jamf recon -saveFormTo /tmp/

    There will now be a file in /tmp/ called [machinename].reconForm. Now you can look at the data that is trying to be submitted back. You may wish to reformat the data, so try:

    cat mac118.reconForm | tr "&" " "

    My experience so far with 'There was an error submitting the computer to the JSS. Here is what the JSS reported back:' has been to do with characters that Casper can't handle.

    For example, the '%' symbol causes errors, from incorrect reporting to the above failed to submit. The & symbol in Application names will cause the JSS to fail to submit. You'll notice that from the above cat, a name with a & in it will show as:

    applicationPath=/Applications/Server/Casper Suite 8.3/Documentation %26 Resources/Resource Kit/All Tools/

    This conversion of & to %26 then causes the failed submission. In the past, plugins with the a % in their name caused incorrect reporting of the version numbers of plugins, eg.

    pluginPath=/Applications/Adobe Photoshop CS3/Plug-Ins/Displacement Maps/Random strokes 25%

    So I'd start with doing the reconForm, and then cat the file and grep for %

    cat mac118.reconForm | tr "&" " " | grep "%"

    Find any, then rename them and try again.

    Sean

    J
    Forum|alt.badge.img+3
    • jurgen_linde
    • Author
    • New Contributor
    • December 20, 2011

    My word, Sean, you're absolutely correct. During my testing I enabled
    On Tue, Dec 20, 2011 at 1:34 PM, Sean Holden <Sean.Holden at framestore.com> wrote:
    the function to add fonts as part of the inventory collection. I didnt
    find any % signs in my report, but I do know there are some chinese
    character fonts by default installed on OS X Lion, guess 10.6 as well,
    but after I disabled it to collect fonts, the problem vanished.

    How come this is still a problem though? One would think JAMF would
    have fixed such a silly problem long time ago? It's surely not that
    hard. Question still remain though... why can Recon.app submit it
    properly, but not the command in terminal?

    Terms & ConditionsCookie settingsAccessibility statement