reposado suddenly unavailable due to NSURLErrorDomain error -1100 ?!?

[david koff]

logs are normal, nightly repo_sync is working without a hitch and not showing any errors. command line and margarita are both working to manage our two branches. so, to be honest: i don't think that our issue is with the reposado service itself.

but suddenly, none of our macs can see the updates or download what they need. i've tested changing the catalogURL on the SoftwareUpdate.plist on our macs and pointing them to either of these branches' catalogs... but both provide the same error when running software update. from the command line:

sh-3.2# softwareupdate -laSoftware Update Tool

Copyright 2002-2010 Apple

The operation couldn’t be completed. (NSURLErrorDomain error -1100.)

checked the server app and the web server service: all looks good and unchanged there. it's up and running and serving up the /html folder (not the parent folder which also contains the /metadata directory) as we always have and made that available to all users. port is 8088.

other things to note: i can't see the catalog if i point my browser to any of the following:

http://ourdomain.edu:8088/content/catalogs/others/index-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog

http://ourdomain.edu:8088/content/catalogs/index-1_production.sucatalog

other things i've tried/tested:

+ flushed mDNSResponder in case we had issues with the name resolving

+ pointed back to apple to test the softwareupdate mechanism - works just fine

so something is up. open to any suggestions. 

[Gregory Neagle]

On Feb 5, 2013, at 4:31 PM, david koff <davi...@gmail.com> wrote:

logs are normal, nightly repo_sync is working without a hitch and not showing any errors. command line and margarita are both working to manage our two branches. so, to be honest: i don't think that our issue is with the reposado service itself.

but suddenly, none of our macs can see the updates or download what they need. i've tested changing the catalogURL on the SoftwareUpdate.plist on our macs and pointing them to either of these branches' catalogs... but both provide the same error when running software update. from the command line:

sh-3.2# softwareupdate -laSoftware Update Tool

Copyright 2002-2010 Apple

The operation couldn’t be completed. (NSURLErrorDomain error -1100.)

checked the server app and the web server service: all looks good and unchanged there. it's up and running and serving up the /html folder (not the parent folder which also contains the /metadata directory) as we always have and made that available to all users. port is 8088.

other things to note: i can't see the catalog if i point my browser to any of the following:

http://ourdomain.edu:8088/content/catalogs/others/index-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog

http://ourdomain.edu:8088/content/catalogs/index-1_production.sucatalog

This is a pretty big clue that your web server is _not_ serving the URLs needed.

-Greg

other things i've tried/tested:

+ flushed mDNSResponder in case we had issues with the name resolving

+ pointed back to apple to test the softwareupdate mechanism - works just fine

so something is up. open to any suggestions. 

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

[david koff]

thanks for the rapid response, greg. i've been troubleshooting the web server interface on lion server and it's being.... well, it's acting like a teenager. how's that for polite?

d

[Nate]

What has changed since it worked last?  Did you add any sites recently?

Nate

--

[david koff]

i did, actually: i added an adobe AUSST library. but in a different location. entirely with it's own separate entry in the server.app. but we're not yet running the AUSST so i can delete that and see if it makes a difference.

david

[david koff]

nate, i deleted the adobe AUSST web share and boom: reposado suddenly started working again. why IS it that adobe's stuff always seems to mess with everything that i do?!?

cheers, everyone. 

d

On Tuesday, February 5, 2013 6:31:57 PM UTC-6, david koff wrote:

[david koff]

just for the sake of embarrassing disclosure: the REASON why the adobe AUSST web share had caused problems with reposed was simple: both were using the same port: 8088. i know, i know... freshman mistake but that seems to be the root of the problem. so for those that read this thread, the issue isn't adobe: it's yours truly botching a port number.

:-)