Error 23: Failed writing body (0 != 1440) - What is this?

8,309 views
Skip to first unread message

costasppc

unread,
Nov 15, 2012, 5:16:24 AM11/15/12
to repo...@googlegroups.com
Nov 15 12:13:47 Could not replicate http://swscan.apple.com/content/catalogs/others/index-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog: Error 23: Failed writing body (0 != 1440)

Is it a disk space issue or something with Apple Update catalogs?

Best regards

Kostas

costasppc

unread,
Nov 17, 2012, 6:43:30 AM11/17/12
to repo...@googlegroups.com
Any replies, please?

Thanks

Kostas

Gregory Neagle

unread,
Nov 17, 2012, 1:47:04 PM11/17/12
to repo...@googlegroups.com
On Nov 17, 2012, at 3:43 AM, costasppc <cost...@gmail.com> wrote:

Any replies, please?

Thanks

Kostas

On Thursday, November 15, 2012 12:16:24 PM UTC+2, costasppc wrote:
Nov 15 12:13:47 Could not replicate http://swscan.apple.com/content/catalogs/others/index-mountainlion-lion-snowleopard-leopard.merged-1.sucatalog: Error 23: Failed writing body (0 != 1440)

Is it a disk space issue

You would be in a better position to determine that than us. Is the disk on which you are storing your reposado update cache full? A catalog doesn't require much space, so it would have to be very full indeed.

or something with Apple Update catalogs?

If you've eliminated a disk space or write permissions problem, have you tried to sync again?


Best regards

Kostas

Kostas Backas-Gmail

unread,
Nov 17, 2012, 6:29:31 PM11/17/12
to repo...@googlegroups.com
Thank you. No, the disk is not full (has around 20 GBs free). Had no permissions issues before with Reposado updates.

Best regards

Kostas

Joe Wollard

unread,
Nov 17, 2012, 11:32:38 PM11/17/12
to repo...@googlegroups.com
The error that you're getting is from curl. I believe curl is trying to tell you that it thought it wrote 1440 bytes (its default buffer size, I think) when in fact it wrote 0 bytes.

So, what happens if you try


(don't omit the '-' at the end) That should give you a ton of output, most of which will be the sucatalog. If not, it should give you some error messages that might help with the troubleshooting process.
--
Joe Wollard

Joe Wollard

unread,
Nov 17, 2012, 11:36:13 PM11/17/12
to repo...@googlegroups.com
I guess I should be a little more verbose. My thought behind using the curl command is to isolate the issue to curl as well as to eliminate an inability to download the file as a possibility. The latter seems unlikely, but if you're sure you don't have permissions issues _and_ your disk isn't full, I'm not sure what to tell you.
--
Joe Wollard

Reply all
Reply to author
Forward
0 new messages