Chrome causes Autopkgr to hang at "Run AutoPkg Now" #230
Comments
|
autopkg run recipe1.munki recipe2.munki recipe3.munki etc.
|
|
Hi @kylevitale - What are the results of |
|
And try Which is almost exactly the invocation AutoPkgr uses |
|
A-Team-01:~ kvitale$ which autopkg A-Team-01:~ kvitale$ which git And the below command returns the autopkg help command list. /usr/bin/python /usr/local/bin/autopkg --recipe-list On Thu, Dec 4, 2014 at 5:53 PM, Elliot Jordan notifications@github.com
|
|
Sorry I missed the verb, it should be this... /usr/bin/python /usr/local/bin/autopkg run --recipe-list ~/Library/Application\ Support/AutoPkgr/recipe_list.txt --report-plist /tmp/run.out.txt |
|
Output of tmp/run.out.txt: failures new_downloads/Users/kvitale/Library/AutoPkg/Cache/local.munki.AdobeAir/downloads/AdobeAIR.dmg /Users/kvitale/Library/AutoPkg/Cache/local.munki.AdobeFlashPlayer/downloads/AdobeFlashPlayer.dmg /Users/kvitale/Library/AutoPkg/Cache/local.munki.AdobeAir/AdobeAIR-15.0.0.356.pkg On Fri, Dec 5, 2014 at 9:39 AM, Eldon Ahrold notifications@github.com
|
|
Ok, so that checks out. So when you click "Check Apps Now" I'm guessing the "Cancel" button shows, but doesn't do anything correct? After you click "Check Apps Now" Go into the terminal an check to see if by any chance did get launched Also when you click "Cancel" do you see this message in the log? |
|
Yes, when I press cancel, a message shows in the log but doesn't do When I run that command via terminal it just returns back "grep autopkg". On Fri, Dec 5, 2014 at 10:09 AM, Eldon Ahrold notifications@github.com
|
|
These showed up in the log, too: 12/5/14 10:11:04.066 AM secd[794]: securityd_xpc_dictionary_handler 12/5/14 10:11:04.067 AM AutoPkgr[90734]: SecOSStatusWith error:[-34018] On Fri, Dec 5, 2014 at 10:14 AM, Kyle Vitale kvitale@gmail.com wrote:
|
|
And this one: 12/5/14 10:10:49.961 AM com.apple.launchd.peruser.533491042[663]: On Fri, Dec 5, 2014 at 10:16 AM, Kyle Vitale kvitale@gmail.com wrote:
|
|
The SecOSStatus erros, are fine, they're just an issue regarding the keychain and don't actually effect anything. This one just indicates you force quit the app. So at this point I'm somewhat stumped. We did see a similar issue a while ago #126, but I thought we were in the clear. We never could figure out what was going on. We've done some substantial improvements on the back end that triggers autopkg for the 1.2 release. It's in the early stages, but would you mind seeing if this resolves your issue? https://github.com/eahrold/autopkgr/releases/tag/v1.2-alpha-dict Please take heed of the Notes on the release page. Especially the backing up of you recipe-list file and the uninstalling of the helper tool. -Thanks |
|
That release didn't work... And issue #126 is exactly what I am seeing. I On Fri, Dec 5, 2014 at 10:35 AM, Eldon Ahrold notifications@github.com
|
|
Man, that's bad news. We never did figure it out, and that was one of our main developer's machine. There's absolutely nothing you can think of that changed on your system between the day it was working and the day it stopped. Any installs, configuration changes to your laptop, software updates, anything at all? What os version are you running? |
|
Progress! Something in Google Chrome (Beta ver 40) was causing this. One of I had restarted my machine (10.9.5 fully patched) and Autopkgr started On Fri, Dec 5, 2014 at 11:00 AM, Eldon Ahrold notifications@github.com
|
|
Wow, good troubleshooting @kylevitale ! |
|
@futureimperfect is chrome your browser of choice too? could this be the same thing you had happening? |
|
@kylevitale I would like to second @homebysix's thumbs up. I have no idea how chrome could inject itself between NSTask (AutoPkr) and python, but that's scary. Thanks, |
|
I'll let you know when/if I find anything more. It happened again yesterday, but I didn't have time to look into it. |
|
More progress! My setup: Google Chrome Beta ver 40. OS X 10.9.5. Autopkgr 1.2-alpha (558). It appears related to multiple users, gmail, and Chrome. I have two Chrome "People" to keep personal and work accounts separate. I use gmail for both work and personal accounts, and have tabs for both inboxes open. If both Chrome "People" have gmail open, Autopkgr hangs. If I close either gmail tab, Autopkgr works fine. |
|
@kylevitale Wow, that's oddly specific. I also have multiple Chrome users, and I opened two Gmail windows simultaneously and had no issues. I'm on Chrome 39.0.2171.71. So maybe there's more to it. Do you have any Chrome extensions or Gmail labs features enabled? |
|
I just went up to chrome 40 and tried to reproduce, no luck. |
|
I tried the same thing on another machine with Chrome 39, but couldn't It's weird because I can reproduce it every time with two gmail tabs open. On Tue, Dec 9, 2014 at 11:54 AM, Eldon Ahrold notifications@github.com
|
|
I have the same issue, "Running selected Autopkg recipes" stalls, has to be force quit, independent of Chrome |
|
@predrags does it happen If all other apps are closed? What do you have in your |
|
Correct, I've tried quitting all apps, fresh reboot etc...here are the contents of my Launch folders: Index of /Library/LaunchDaemons/ Index of /Library/LaunchAgents/ |
|
@kylevitale can you provide me a list with the LaunchD's you have installed. I'd like to see if there's some overlap that may be causing the issue. |
|
Here you go. Sorry for the delay. /Library/LaunchDaemons: /Library/LaunchAgents: |
|
@kylevitale, @predrags, Other than that, do either of you ever build from source using Xcode? I could guide you through some debugging. |
|
@gerardweese, @kylevitale, @ToddToddTodd |
|
@eahrold I have only seen it on "Check Apps." |
|
@eahrold https://github.com/eahrold Only on "Check Apps Now", "Update On Wed, Jan 7, 2015 at 4:55 PM, gerardweese notifications@github.com
|
|
@kylevitale, @gerardweese ... So I've reworked some more things to hopefully address this. There are two separate versions here, one that forces python to run in i386 mode and one that forces it to run in x86_64. Pleas try both and see if either work. It also changes the way the file handles that provide progress updates are setup. I saw that cause a similar issue in another situation. Thanks again, --Eldon |
|
@eahrold Closing Chrome does fix the issue |
|
@eahrold I'm sorry to report the issue still exists on both versions. Since we now have an option to cancel and we know a simple work around of closing Chrome I'm willing to move on. |
|
@gerardweese Could you test again on the latest beta 1.2-rc1? Just want to see if the behavior remains consistent. |
|
Sure, I will take a look on Monday; I have been running the 1.2 beta for a month I will try the rc. -Gerard — On Fri, Feb 6, 2015 at 10:22 AM, Elliot Jordan notifications@github.com
|
|
@gerardweese 1.2 final release is out now. |
homebysix
changed the title
|
@homebysix this is still an issue. I can still work around it by closing Chrome, and the cancel button works. Not a huge source of pain. |
|
It hasn't been happening for me. On Mon, Mar 9, 2015 at 8:39 PM, gerardweese notifications@github.com
|
|
Still happens for me. AutoPkgr 1.2.1 (726) on 10.9.5 w/ latest Chrome 41. |
|
It's still happening for me on AutoPkgr Version 1.2.1 (726) & OS 10.10.2 & Chrome 41.0.2272.89 (64-bit) |
eahrold
changed the title
|
@homebysix, The AutoPkg(r) runInBackground could also stall the same way that "Run AutoPkg Now" does. If that occurred launchd wouldn't run the job on it's subsequent schedule since the previous run never exited. I've got two ideas as to how to deal with this. 2 - Add a similar check in the LGAutoPkgTask that acts as a timeout timer and if the actual I'm pretty sure the first would work and it's something I could test. The second has the benefit of addressing both background runs and "Run AutoPkg Now" as well as sending back an error, but since I haven't been able to reproduce this situation it'd be another stab in the dark as to it's actual functioning. Are you able to replicate this with any regularity? If so I'll start putting up some builds, and we can test out some of these techniques. Thoughts? And @da4ftso , @ToddToddTodd , @gerardweese |
|
@eahrold Chrome is starting to block AutoPkgr pretty regularly lately. I've tried closing one tab at a time and re-running to see if it's related to a particular tab or website, but the problem persists even if Chrome doesn't have any windows open at all. Feel free to branch/build and I'll test. |
|
@kylevitale, @ToddToddTodd , @gerardweese , @da4ftso , @jhowe-sgs, @jumpkick, @Tecnico1931 Good news! I think we got this fixed. Long story short, we currently think the problem wasn't Google Chrome's injecting anything into python or autopkgr as we initially suspected, but rather it's unusual practice of creating so many "Goolge Chrome Helper" processes each with such astoundingly long launch arguments. (just run Ultimately this was causing the stdout buffer of the NSTask to fill up and wait to be flushed, resulting in a the stall. We would love your feedback and help testing out this new version. |
|
Nice job @eahrold! This was such an annoying bug. Glad that it's squashed! |
Autopkgr no longer runs for me and I am not sure why. When I run it I get the "Running selected Autopkg updates" status but no updates are ever process, nor does this window ever mention that recipes were processed. In the past I would see the update currently being processed such as "puppet.munki 2/12" or something similar. Now the message never changes and I have to force quit autopkgr.
I have tried deleting all known files from caches, prefs, app support, saved states, etc (not sure if I found them all) but I still can't get it to run.
Running autopkg from command line works just fine.
I enabled Verbose logs but nothing shows up there. It just stalls.
Any idea where I can go from here?
The text was updated successfully, but these errors were encountered: