-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not load models from jamf #15
Comments
What happens If you change line 1012 from |
Thanks! I'll give this a try tomorrow! |
Ah, still the same error:
Anything else I can try? Thanks! Mike |
Hi Mike, this is the command I am using notice the "=" |
Thanks, @macinandy. I made the changes, but they don't seem to have helped - here's the
I also changed Caching Servers so that's why the ports are different. I also added Also: I know the ReadMe says to put precache.py in Thanks again for the help! Mike |
Hi again, try removing the https from your jamfserver as in
/usr/local/precache/precache.py --cache-server http://my.server.tld:49240 --jamfserver=my.jss.tld:8443 --jamfuser=myusername --jamfpassword=mypassword
no it won’t matter where you place precache, it is just cleaner if you put it in /usr/local/bin/
thanks
… On 17/05/2017, at 8:49 AM, Mike Solin ***@***.***> wrote:
Thanks, @macinandy <https://github.com/macinandy>. I made the changes, but they don't seem to have helped - here's the bash -x output. I added some variables, but nothing too fancy.
+ precache=/usr/local/precache/precache.py
+ caching_server_1=http://my.server.tld:49240
+ jamf_server=https://my.jss.tld:8443
+ jamf_user=myusername
+ jamf_password=mypassword
+ /usr/local/precache/precache.py --cache-server http://my.server.tld:49240 --jamfserver=https://my.jss.tld:8443 --jamfuser=myusername --jamfpassword=mypassword
precache version 1.1.2
Caching Server: http://my.server.tld:49240
Processing feeds. This may take a few moments.
Can not load models from jamf: <urlopen error [Errno 8] nodename nor servname provided, or not known>
+ exit 0
I also changed Caching Servers so that's why the ports are different. I also added --debug, but that just added more output to /tmp/precache.log. I don't see any hints that indicate what went wrong.
Also: I know the ReadMe says to put precache.py in /usr/local/bin, but do you think it's okay that I'm using /usr/local/precache instead? That way, I can do a git pull prior to running the script.
Thanks again for the help!
Mike
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#15 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD8H_X2abg5R_4OJCe4vStd0RWJgoPDNks5r6gvmgaJpZM4NbZCB>.
|
Oops! I understand now. I had changed it from It's working! Thank you! Do you think I can return line 1012 in precache.py back to normal? Mike |
Hi @macinandy - I updated my copy of
I returned line 1012 to the code you mentioned in #15 (comment) and it's processing iOS device models properly again. Would it be possible to merge this code change to the master branch, or would that break other things? Thanks! Mike |
@flammable @macinandy check out Either of the below will work (may need to If you prefer to manage python dependancies by using You don't have to put EDIT |
Thanks for this script! I'm finally getting around to running it via launchd. The Jamf Pro functionality looks perfect - it sure beats listing the model IDs manually in the script, which was my original plan. 😄
I'm running into a weird error, though - any idea?
I created a new JSS user, and gave them the ability to read Mobile Devices. Here's the command I'm running:
/usr/local/precache/precache.py --cache-server http://my.server.tld:49240 --jamfserver https://my.jss.tld:8443 --jamfuser myusername --jamfpassword mypassword
Here's the
bash -x
output:The JSS URL is reachable from the server that's running this script - I was able to load the URL in Safari with no issues. Any idea what could be wrong?
Thanks!
Mike
The text was updated successfully, but these errors were encountered: