post flight stderr (and more) on scripts v .0.8.0 and beyond

Stephen Cranfill

unread,

Feb 24, 2016, 6:52:36 AM2/24/16

to sal-discuss

Greetings,

I'm running the latest WIP SAL build and as soon as I upgrade from the .0.7.5 version of the scripts package, I get the following:

Finishing...

Performing postflight tasks...

postflight stderr: Traceback (most recent call last):

File "/usr/local/munki/postflight.d/sal-postflight", line 489, in <module>

main()

File "/usr/local/munki/postflight.d/sal-postflight", line 60, in main

send_checkin(ServerURL, copy.copy(submission), report)

File "/usr/local/munki/postflight.d/sal-postflight", line 392, in send_checkin

send_report(checkinurl, checkin_data)

File "/usr/local/munki/postflight.d/sal-postflight", line 378, in send_report

encoded_data = urllib.urlencode(report)

File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib.py", line 1347, in urlencode

v = quote_plus(str(v))

UnicodeEncodeError: 'ascii' codec can't encode character u'\u2019' in position 10: ordinal not in range(128)

Done.

I've tried this with the both 2.4 official release and the 2.5 release version of Munkitools with the same result.

This is on a 10.11.3 machine.

As soon as I reinstall the .0.7.5 scripts version, the error goes away and the machine reports properly again.

Any ideas?

Cheers,

Stephen

Graham Gilbert

unread,

Feb 24, 2016, 7:00:18 AM2/24/16

to sal-discuss

What's the output of running munki with - vvv?

Sent from my iPhone

--
You received this message because you are subscribed to the Google Groups "sal-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sal-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Stephen Cranfill

unread,

Feb 24, 2016, 8:10:40 AM2/24/16

to sal-discuss

There was quite a bit of output, so I've attached it as a file. I started at the post flight output.

Cheers,

Stephen

Output.txt

Stephen Cranfill

unread,

Feb 24, 2016, 8:56:55 AM2/24/16

to sal-discuss

Sorry to slam you with data, but I just imaged a brand new machine to test. It has 10.11.3, RC 2.5 of Munkitools and .091 of SAL Scripts. The error isn't quite the same as with the machine I mentioned above, but nevertheless it never reports into SAL. I think the salient bit might be below, but I'll attach the full output as well.

Note I've tried this with two different freshly imaged machines running 10.11.3 with the same results. I've also tried the official 2.4 release of Munkitools and .0.7.5 of SAL scripts on these freshly imaged machines and they still won't report into SAL.

Cheers,

Stephen

</plist>

Puppet Version:

Facter Output:

{}

Checkin Response:

<html>

<head><title>502 Bad Gateway</title></head>

<center><h1>502 Bad Gateway</h1></center>

<hr><center>nginx/1.4.6 (Ubuntu)</center>

</body>

</html>

Hashed Report Response:

Serial Number not found

Install.log Response:

Machine not found

<?xml version="1.0" encoding="UTF-8"?>

Freshly Imaged.rtf

Stephen Cranfill

unread,

Feb 24, 2016, 11:40:10 AM2/24/16

to sal-discuss

I just rolled back to 2.4.0.555 from the latest WIP and one issue has cleared up.

The issue I had with the WIP version only appeared to occur with brand new machines that had never reported before. That is, if the machine was already in SAL, then it would would update properly, even with the WIP version. If it wasn't already in there, I'd get the output included in the previous post and the machine would never show up in SAL.

So, running latest Munkitools and latest SAL script version all's well with new machines. The machine referenced in the first post still has the same issue with 0.9.1, but I'm far less worried about that since it's a one-off. Rolling back to 0.7.5 on that one still makes it work properly.

Cheers,

Stephen

Graham Gilbert

unread,

Feb 24, 2016, 4:10:16 PM2/24/16

to sal-discuss

Ok, so 502 is a server error. It could be anything, since WIP is really only intended for developers contributing to Sal. It definitely is a work in progress, so there will almost certainly be bugs in it. I'll take a look at this when I get some airport time on Friday. Hopefully it will be simple!

Sent from my iPhone

Reply all

Reply to author

Forward