Opened 9 years ago
Closed 9 years ago
#49224 closed defect (fixed)
rsync.macports.org server Input/output errors
| Reported by: | master.alff@… | Owned by: | admin@… |
|---|---|---|---|
| Priority: | High | Milestone: | |
| Component: | server/hosting | Version: | |
| Keywords: | Cc: | skidspam@…, ryandesign (Ryan Carsten Schmidt), neverpanic (Clemens Lang), blair (Blair Zajac), rnspayne@…, Themanwithoutaplan, mojca (Mojca Miklavec), robin.newman@…, listmeister@…, ishtar@…, macports@…, djlambert (Derek J. Lambert), cjones051073 (Chris Jones), peter.mcalpine@…, leeawalsh@…, smparkes@…, harry.weppner@…, vcultharris (L.T. Harris), alan.mock@…, francwalter@…, ryan.d.jamison@…, ghlecl (Ghyslain Leclerc), jrjsmrtn, stephenhamilton@…, petrrr, erich3@…, michaelwallis@…, p.perroud@…, hippallium-macports@…, jonasjonas (Frank Hellenkamp), alex.emergy@…, jsalort (Julien Salort), Feuermurmel (Michael Schwarz), joseph.c.slater@…, fracai, breun (Nils Breunese), davidwalton3142@…, Geoffrey@…, steve.sell@…, marco-comini (Marco Comini), rohall@… | |
| Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
I've installed latest one MacPorts 2.3.4. And i then i tried to update port tree by 'selfupdate' action and i've got this exception:
$sudo port -fv selfupdate
---> Updating MacPorts base sources using rsync
receiving file list ... done
sent 36 bytes received 69 bytes 42.00 bytes/sec
total size is 27013120 speedup is 257267.81
receiving file list ... done
sent 36 bytes received 76 bytes 32.00 bytes/sec
total size is 512 speedup is 4.57
MacPorts base version 2.3.4 installed,
MacPorts base version 2.3.4 downloaded.
---> Updating the ports tree
Synchronizing local ports tree from rsync://rsync.macports.org/release/ports/
receiving file list ... rsync: readlink_stat("/ports/kde/kde-l10n-eu/files/patch-CMakeLists.txt.diff" (in release)) failed: Input/output error (5)
rsync: readlink_stat("/ports/science/viking/files/autogen.sh" (in release)) failed: Input/output error (5)
rsync: readlink_stat("/ports/science/ghemical/files/patch-autogen.sh.diff" (in release)) failed: Input/output error (5)
rsync: readlink_stat("/ports/science/bedtools/Portfile" (in release)) failed: Input/output error (5)
rsync: readlink_stat("/ports/science/swarm/files/patch-libpng-1.5.diff" (in release)) failed: Input/output error (5)
rsync: readlink_stat("/ports/science/ldas-tools/files/patch-libraries-ldastoolsal-src-AtExit.cc.diff" (in release)) failed: Input/output error (5)
rsync: readlink_stat("/ports/audio/sptk/Portfile" (in release)) failed: Input/output error (5)
rsync: readlink_stat("/ports/textproc/unicode/Portfile" (in release)) failed: Input/output error (5)
rsync: readlink_stat("/ports/sysutils/augeas/files/yosemite-libtool.patch" (in release)) failed: Input/output error (5)
rsync: readlink_stat("/ports/sysutils/libfaketime/Portfile" (in release)) failed: Input/output error (5)
rsync: readlink_stat("/ports/tex/blahtexml/files/patch-main.cpp.diff" (in release)) failed: Input/output error (5)
rsync: readlink_stat("/ports/x11/xtide/files/patch-configure.ac.diff" (in release)) failed: Input/output error (5)
done
IO error encountered -- skipping file deletion
sent 53 bytes received 815768 bytes 148331.09 bytes/sec
total size is 42073152 speedup is 51.57
rsync error: some files could not be transferred (code 23) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/main.c(1400) [generator=2.6.9]
Command failed: /usr/bin/rsync -rtzv --delete-after '--exclude=/PortIndex*' rsync://rsync.macports.org/release/ports/ /opt/local/var/macports/sources/rsync.macports.org/release/ports
Exit code: 23
Error: Synchronization of the local ports tree failed doing rsync
Error: Couldn't sync the ports tree: Synchronization of 1 source(s) failed
To report a bug, follow the instructions in the guide:
http://guide.macports.org/#project.tickets
Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the ports tree: Synchronization of 1 source(s) failed
After that i couple of times tried to delete port tree, reinstall again and tried to download failed ports manually:
$ rsync -rtvz rsync://rsync.macports.org/release/ports/kde/kde-l10n-eu ./
receiving file list ... rsync: readlink_stat("/ports/kde/kde-l10n-eu/files/patch-CMakeLists.txt.diff" (in release)) failed: Input/output error (5)
done
kde-l10n-eu/
kde-l10n-eu/Portfile
kde-l10n-eu/files/
sent 70 bytes received 958 bytes 293.71 bytes/sec
total size is 1125 speedup is 1.09
rsync error: some files could not be transferred (code 23) at /BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-47/rsync/main.c(1400) [generator=2.6.9]
So it seems something broken on server side?
Change History (52)
comment:3 follow-up: 4 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… cal@… blair@… added |
|---|---|
| Component: | ports → server/hosting |
| Description: | modified (diff) |
| Keywords: | selfupdate removed |
| Owner: | changed from macports-tickets@… to admin@… |
| Priority: | Normal → High |
| Summary: | port selfupdate can not update because broken ports → rsync.macports.org server Input/output errors |
| Version: | 2.3.4 |
I have not seen this problem myself, but it has been reported on the mailing list as well.
Keith, can you please check the rsync server? Has its disk failed?
The rsync server is critical to MacPorts. Without it, users cannot get any updates.
comment:4 follow-up: 30 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to ryandesign@…:
I have not seen this problem myself, but it has been reported on the mailing list as well.
Now I understand why I haven't seen it. My sources.conf is set to use
rsync://rsync.macports.org/release/tarballs/ports.tar
which is complete but out of date. Users with older macports installation who haven't updated their sources.conf since r79599 still use
rsync://rsync.macports.org/release/ports/
where the input/output errors can be seen (and are likely what's causing the server-side process that repackages the tarball to be interrupted as well).
comment:5 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
Users can either wait until the server is fixed, or else switch to a different syncing method, such as an svn working copy or a tarball via https.
Edit: the https tarball isn't being updated either.
comment:30 follow-up: 31 Changed 9 years ago by michaelwallis@…
Replying to ryandesign@…:
Replying to ryandesign@…:
I have not seen this problem myself, but it has been reported on the mailing list as well.
Now I understand why I haven't seen it. My sources.conf is set to use
rsync://rsync.macports.org/release/tarballs/ports.tarwhich is complete but out of date. Users with older macports installation who haven't updated their sources.conf since r79599 still use
rsync://rsync.macports.org/release/ports/where the input/output errors can be seen (and are likely what's causing the server-side process that repackages the tarball to be interrupted as well).
So what should we be using? And what's the next step, as all my machines are down and failing.
comment:31 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | michaelwallis@… added |
|---|
Replying to michaelwallis@…:
So what should we be using? And what's the next step, as all my machines are down and failing.
See comment:5.
comment:41 follow-up: 42 Changed 9 years ago by davidwalton3142@…
| Cc: | davidwalton3142@… added |
|---|
Cc Me!
comment:45 Changed 9 years ago by steve.sell@…
I'm trying to do a new install - is there a way to get base updated?
comment:47 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
If you're doing a new install, you already have the latest base. If your base is not the latest (i.e. is earlier than 2.3.4) you can update to 2.3.4 by downloading the MacPorts installer from the web site. To update ports, switch to syncing with svn instead of rsync.
comment:48 follow-ups: 49 52 Changed 9 years ago by keith_dart@…
The disk on that machine (a virtual disk) had a lot of file system corruption. Not sure how that happened, but it had been recently migrated to a new host. The file system is now repaired but I can't tell what files have been lost. There is nothing in /lost+found.
comment:49 follow-up: 50 Changed 9 years ago by francwalter@…
Replying to keith_dart@…:
The disk on that machine (a virtual disk) had a lot of file system corruption. Not sure how that happened, but it had been recently migrated to a new host. The file system is now repaired but I can't tell what files have been lost.
Does that definetly mean the best is to switch to syncing with svn now?
comment:50 Changed 9 years ago by cjones051073 (Chris Jones)
Replying to francwalter@…:
Replying to keith_dart@…:
The disk on that machine (a virtual disk) had a lot of file system corruption. Not sure how that happened, but it had been recently migrated to a new host. The file system is now repaired but I can't tell what files have been lost.
Does that definetly mean the best is to switch to syncing with svn now?
Currently, no, due to yet another issue ...
comment:52 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Replying to keith_dart@…:
The disk on that machine (a virtual disk) had a lot of file system corruption. Not sure how that happened, but it had been recently migrated to a new host. The file system is now repaired but I can't tell what files have been lost. There is nothing in /lost+found.
Thanks. Hopefully that means nothing has been lost...
+1 exact same problem