Job failed to exec(3) for weird reason (literally!)

[blackthorne]

com.apple.launchd1 : (com.jensen.iRE.Startup) Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
com.apple.launchd1 : (com.jensen.iRE.Startup) Job failed to exec(3) for weird reason: 2
iRE2[380] : In finally block.

Thank you,
Francisco

[S3Jensen]

Francisco,
If you ssh into the device and manually start the iRE_Server.py script. Then launch the web UI, what information does it tell you?

Regards,
Steve

Date: Wed, 30 Jul 2014 07:42:16 -0700
From: notifications@github.com
To: iRET@noreply.github.com
Subject: [iRET] Job failed to exec(3) for weird reason (literally!) (#2)

com.apple.launchd1 : (com.jensen.iRE.Startup) Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory

com.apple.launchd1 : (com.jensen.iRE.Startup) Job failed to exec(3) for weird reason: 2

iRE2[380] : In finally block.

Thank you,

Francisco

—
Reply to this email directly or view it on GitHub.

[blackthorne]

S3Jensen,
I was able to fix this, it was a broken dependency. Not sure which though as I rebuilt all of them.
Still, there is room to improving the logging messages in there... :)

Thank you

[S3Jensen]

Francisco,
Was the issue with an iRET dependency or with one of the actual tools (theos, dumpdecrypted, etc) intergrated within iRET?

Regards,
Steve

Date: Wed, 30 Jul 2014 15:41:42 -0700
From: notifications@github.com
To: iRET@noreply.github.com
CC: sjensen1207@hotmail.com
Subject: Re: [iRET] Job failed to exec(3) for weird reason (literally!) (#2)

S3Jensen,

I was able to fix this, it was a broken dependency. Not sure which though as I rebuilt all of them.

Still, there is room to improving the logging messages in there... :)

Thank you

—
Reply to this email directly or view it on GitHub.

[blackthorne]

I can't say for sure but my guess would be that it was the wrong python interpreter since it's an error that happens right in the beginning. There are no other log messages before those that I pasted to you.

[blackthorne]

Ok, I just confirmed. It was python. I can reproduce it. Look:

# mv /usr/bin/python{,_broken}
# socat - UNIX-CONNECT:/var/run/lockdown/syslog.sock

 ========================
ASL is here to serve you
 > watch
...

Now I start the app and I see:

Jul 31 00:59:00 XXX com.apple.launchd[1] (com.jensen.iRE.Startup[3465]) <Notice>: (com.jensen.iRE.Startup) Job failed to exec(3). Setting up event to tell us when to try again: 2: No such file or directory
Jul 31 00:59:00 XXX com.apple.launchd[1] (com.jensen.iRE.Startup[3465]) <Notice>: (com.jensen.iRE.Startup) Job failed to exec(3) for weird reason: 2
Jul 31 00:59:00 XXX iRE2[473] <Warning>: In finally block.

Cheers,
Francisco