Buy hash Osterhout

__________________________

📍 Verified store!

📍 Guarantees! Quality! Reviews!

__________________________

▼▼ ▼▼ ▼▼ ▼▼ ▼▼ ▼▼ ▼▼

▲▲ ▲▲ ▲▲ ▲▲ ▲▲ ▲▲ ▲▲

Buy hash Osterhout

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. The image specified to use for the notary service is a specific CI build that is really old, and no new versions are being built since the CI has changed. The test fixture certs included have since expired, so it no longer works. I am not aware of there being any newer images that include the test fixture certs, so I'm not really sure how best to suggest updating this. The easy way to get a working environment with the test fixture certs is to clone the notary repo, and use it's docker-compose file. However that docker-compose file lacks the registry and docker-in-docker images that the DCT sandbox wants. HuKeping justincormack As the people who seem to merge PRs for notary in recent times any thoughts? The goal being to have some easy way to set up some environment where users can test the workflow of DCT, without needing to jump through all the hoops of setting up certs for notary. A set of steps that actually works to create a working sandbox environment right now is below. The concern I have with suggesting this is that it could easily become out of date if changes are made to the notary repository, since the below steps are run in the cloned notary repository to be able to access the test fixture certs, but the compose file would live in the documentation, and thus be easier to forget to update. Alternatives include be adding a compose file for this scenario to the notary repo, or having some published image with the test fixture certs available. The text was updated successfully, but these errors were encountered:. It's a rework of the existing script to run outside of the git repo:. Sorry, something went wrong. There hasn't been any activity on this issue for a long time. If not, this issue will be closed in 14 days. This helps our maintainers focus on the active issues. Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues. Skip to content. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. You switched accounts on another tab or window. Dismiss alert. Notifications You must be signed in to change notification settings Fork 7. New issue. Sign up for GitHub. Jump to bottom. Copy link. KevinCathcart commented Jan 27, All reactions. It's a rework of the existing script to run outside of the git repo:! IAL32 mentioned this issue Nov 30, If you have found a problem that seems similar to this, please open a new issue. Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Search code, repositories, users, issues, pull requests...

Buy hash Osterhout

Then i pointed the build in Apple software updater to my own SUS and the updates installs just fine Back to Munki - seems like it's the iTunes Deactivating them in my own SUS makes all other updates install just fine. So, I'm right now in the process of trying what the next step would be to try. So, i don't know, is it the actual download of the iTunes I'm tempted to reset the SUS one more time to see if the iTunes update start working just like the iPhoto update did. Colin Osterhout. Reply to author. Copy link. Report message. Show original message. Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message. Anyone seen this issue before other than the GP of the initial thread poster? Other things to try? Matt A. I'm running clients with My server is OS X On this machine I also run my own SUS. As you remember apple seem to have had some issues with distributing updates a week ago, so that messed up my own SUS. I did a complete reset of it, let it download all the updates again and started using it. That's when I noticed that my Munki clients all of a sudden couldn't apply apple updates provided by my SUS. Today I've been looking closer at the problem. If you run the managedsoftwareupdate GUI it finds all the updates, but as soon as you try to apply them it shows 'finishing' in just 2 sec and closes down, not updates applied. Running terminal with -vvv shows:. Cheers Matt. Greg Neagle. Is this the case? Is this file missing? Or is there some other issue with the file? If the file is there when this issue occurs and you cannot determine an issue with it, could you forward it to me? I just cleared the Managed Installs folder on one of my clients, activated iTunes I noticed this issue and tested out with curl to make sure I could get the catalog manually, and all seemed well. If not, what sorts of further debug information would be helpful in figuring this out? I'll have a chance here in the next 5 days to test out a couple different ASUS server types Lion and SL at a different location that we work with and will keep the thread posted. This may be the kind of thing that moves me towards trying Reposado. I am having the same problem. Anything figured out yet. I am trying everything I know how to do and I just can't figure it out. Same here, clean Lion install I don't use a Lion Server software update server. I am setting one up to test, but it might be a while, and there's no guarantee that I'll be bale to replicate the issue. So a managedsoftwareupdate -vvvv run demonstrating the issue would be helpful. Or you all should just switch to Reposado. To be clear, I'm running munki against swscan. I'll get you a full log tomorrow. On Jun 28, , at PM, A. I will reset my internal SUS Performing preflight tasks Checking for available updates Retreiving list of software for this machine No changes to managed software are available. Checking Apple Software Update catalog Checking for available Apple Software Updates Caching metadata for product ID zzzz Caching package metadata for product ID zzzz Caching ro distribution for product ID zzzz Caching tr distribution for product ID zzzz Caching ca distribution for product ID zzzz Caching el distribution for product ID zzzz Caching fi distribution for product ID zzzz Caching sv distribution for product ID zzzz Caching German distribution for product ID zzzz Caching hu distribution for product ID zzzz Caching cs distribution for product ID zzzz Caching he distribution for product ID zzzz Caching English distribution for product ID zzzz Caching da distribution for product ID zzzz Caching uk distribution for product ID zzzz Caching ar distribution for product ID zzzz Caching French distribution for product ID zzzz Caching ko distribution for product ID zzzz Caching no distribution for product ID zzzz Caching ru distribution for product ID zzzz Caching Italian distribution for product ID zzzz Caching Dutch distribution for product ID zzzz Caching sk distribution for product ID zzzz Caching Japanese distribution for product ID zzzz Caching th distribution for product ID zzzz Caching pt distribution for product ID zzzz Caching hr distribution for product ID zzzz Caching Spanish distribution for product ID zzzz Update: I got a local Lion Server Software Update Server up and running and repeated the test s below successfully as well. Arjen van Bochoven. I don't know what I was on yesterday, but I can't replicate the issue anymore. Couldn't find anything in the logs either. Timothy Sutton. Definitely wouldn't be the first time! This is what I have found. Once it is there all seems to work. From what I can tell, at least in my situation, is that disabling the iTunes 6. I then ran Managed Software Update on two other computers without fail. I was then able to activate iTunes 6. The idea I have gleamed from seeing this is that in my situation I had many Apple software updates to install. Below you will find a screenshot of the list that needed to be installed. I am wondering if there is a setting that is holding back installing all that data, and when I deactivated iTunes 6. I am wondering if this has to do with kern. Once I deactivated the iTunes 6. I hope this fully solves my problem and helps with anyone else having this problem. I will let everyone know if I fall into different problems or if the problem resurfaces itself. When I was getting the issue I only had 5 or so updates that were needed to be installed. I should have more data soon since I'm onsite at a different installation and will be rebuilding the network and servers here mostly from scratch. Thanks for the updates! On Jun 29, , at AM, wademade wrote:. The bigger question is why is this file not being written. Another error that would prevent this file from being written is any replication error that occurs while Munki is trying to cache the update metadata. It sounds like this latter issue is what is occurring, based on Arjen's earlier replt, so the larger issue is that Munki is not properly handling this -- it should just stop at that point and not attempt to download any updates since it wasn't able to cache the update metadata. The net result would be the same, though -- Munki would not download or install updates until the issue with the update server was resolved. Most likely there was a problem with the replication of the metadata for the iTunes By excluding that update, Munki could cache the update data for all of the other updates and proceed. That might also explain the issue And I did see the log lines:. I thought that was odd since it got the error code which would seem to indicate success. I've now successfully replicated this issue by disconnecting the network while software update metadata replication was taking place. Net result is the same: Apple software updates won't install, but the error message is something like this:. Failed 7 with: Failed to connect to Couldn't reproduce the failure here on the road with a new installation of Will give another look-see along with the updated code when I get back to my office this upcoming week. Must be something peculiar with my setup at my office. Jul 04 Performing preflight tasks Jul 04 Checking Apple Software Update catalog I think munki should skip this and continue. Gregory Neagle. On Jul 4, , at AM, 'A. That links to a perfectly good file from here. Ben Bass. If you look, apple changed the hosting for swscan. Before it was hosted by apple on a single machine, but now a dns lookup will give you pswscan. If I remember correctly pswscan. If you do a quick dig of swscan. I think they made that change right about the time of the Developer Conference keynote. I addressed this issue in late June -- you can download a build of the Munki tools that has the 'fix' here:. This provides a better error message and prevents Munki from attempting to install Apple updates when it hasn't been able to cache them all for install. But it does not address the underlying issue, which is that there are issues with Apple's software update servers and some files cannot be successfully cached. This is not a problem that can be fixed by modifying Munki; this is an Apple problem. Reposado users have also seen updates that refuse to properly replicate from Apple's servers. Managed Software Update Tool. Munki cannot safely resume downloads without etag support on the web server. Caching metadata for product ID The following Apple Software Updates are available to install:. Getting info on currently installed applications Installing available Apple Software Updates

Buy hash Osterhout