Hi all,
I'm running into a perplexing problem that I've not been able to solve yet, so I'm asking here if anyone has some insight into how to solve this one.
Background: I'm moving off of using Apple's macOS Server SUS in favor of reposado + margarita, as I've become a bit tired of fighting odd issues with Apple's SUS. Setting up reposado and getting updates to sync to the boxes has not been an issue. Everything went pretty smoothly with it for the most part.
The problem: At first, the catalog URLs I set up were working great when I pointed my Mac to them in the com.apple.SoftwareUpdate.plist. I was able to run sudo softwareupdate -l and confirm that it was seeing updates hosted on the Mac running reposado. So far so good, right?
Well, somewhere along the line, this broke on me. Now whenever I run sudo softwareupdate -l it looks like it's checking for updates and then it comes back with
The operation could not be completed. (NSURLErrorDomain error -1100.)As a test, I pointed my Mac back to Apple and ran the command again, and this time it successfully showed me some available updates. So that kind of ruled out a general issue with the softwareupdate command. To confirm I wasn't crazy, I plugged the reposado generated URL my Mac was pointed to into Safari and it loads, perfectly. Even shows as an xml file and everything.
But no matter what I've done, reboots on the server, rebooting my Mac, re-running the repoutil --configure and repo_sync commands, whatever, the above error keeps coming up when I run the softwareupdate --list command on it.
So next I started to think this was an issue with my primary Mac, so I took another test system, running 10.12.6, and pointed it to the same URL. I get the same error when asking it to check for updates. So this means it's not my Mac, but something with reposado or the web site being served. Yet, the full URL loads fine in a browser. Strange!
I have more than one server serving out updates, so I have one or two other servers also synced with updates in reposado. I tried pointing to one of them, despite the server being physically further away from me in EU. Oddly, I get the same error! This means anything running reposado seems to having this problem. I can't fathom why though!
At this point, i'm truly stumped! I just can't figure out what's going on here. These were working fine before and suddenly stopped working, and no measures done so far have brought it back to functionality, on any of the servers I set the product up on.
I've done some searches here and on the web in general, and I pulled up a couple of very old threads of folks facing the same problem, but unfortunately there was no resolution posted on those threads.
Has anyone seen this, and figured out what causes it?
I'm tempted to blow everything away from one of the servers re: reposado and start over, but the repo_sync takes literally days to complete, so I'm really hoping I don't need to do that.
Any suggestions would be greatly appreciated, or I may have to abandon trying to use it if I can't figure out why this isn't working. :(
