metadata corrupt ?!

nORKy

Well-Known Member

Reaction score: 18
Messages: 307

Hi,

I don't known what to do with this error :

Code:
# portsnap fetch update && portversion -l "<"
Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found.
Fetching snapshot tag from portsnap1.freebsd.org... done.
Fetching snapshot metadata... done.
Updating from Mon Dec  8 14:40:05 CET 2008 to Tue Dec  9 07:14:40 CET 2008.
Fetching 3 metadata patches.. done.
Applying metadata patches... done.
Fetching 3 metadata files... /usr/sbin/portsnap: cannot open ca3d1528c2ecc4e2241979fac3ee3ce28ea68f9db12150f8ad3457929e69242d.gz: No such file or directory
metadata is corrupt.

Thanks for your help
 
OP
N

nORKy

Well-Known Member

Reaction score: 18
Messages: 307

Thanks you, it works.

Code:
# rm -Rf /var/db/portsnap/
pc-Joff# portsnap fetch update && portversion -l "<"
portsnap: Directory does not exist or is not writable: /var/db/portsnap
# mkdir /var/db/portsnap
# portsnap fetch update && portversion -l "<"
Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found.
Fetching public key from portsnap2.freebsd.org... done.
Fetching snapshot tag from portsnap2.freebsd.org... done.
Fetching snapshot metadata... done.
Fetching snapshot generated at Tue Dec  9 01:43:15 CET 2008:
7a804d0d777e4786b5a895af34dfa476ff2eeb821d942c  8% of   54 MB  217 kBps 03m55s
 

nabsta

New Member

Reaction score: 9
Messages: 7

I have the same issue, tried it with 4 different servers , same error. It still is amazing why this happened not to just one but 4 of my servers.

Anyways, deleting /var/db/portsnap and repopulating the ports tree helps.

thanks
 

robertclemens

Member

Reaction score: 9
Messages: 39

I have yet to resolve the problem.


[root@abyss /var/db]# rm -rf portsnap
[root@abyss /var/db]# mkdir portsnap
[root@abyss /var/db]# portsnap fetch
Looking up portsnap.FreeBSD.org mirrors... 2 mirrors found.
Fetching public key from portsnap1.FreeBSD.org... done.
Fetching snapshot tag from portsnap1.FreeBSD.org... done.
Fetching snapshot metadata... done.
Fetching snapshot generated at Sun Jan 4 19:38:12 EST 2009:
916e4693ea4689b7598778ef6358f1c2705c84aeaf4a79100% of 55 MB 713 kBps 00m00s
Extracting snapshot... done.
Verifying snapshot integrity... done.
Fetching snapshot tag from portsnap1.FreeBSD.org... done.
Fetching snapshot metadata... fetch: http://portsnap1.FreeBSD.org/t/ef1df878b5fba73256d50b9944b5fb8ee1e9d376fec917a60e52af5e02a861b7: Not Found
sha256: ef1df878b5fba73256d50b9944b5fb8ee1e9d376fec917a60e52af5e02a861b7: No such file or directory
[: !=: unexpected operator
mv: rename ef1df878b5fba73256d50b9944b5fb8ee1e9d376fec917a60e52af5e02a861b7 to tINDEX.new: No such file or directory
done.
grep: tINDEX.new: No such file or directory
look: tINDEX.new: No such file or directory

Portsnap metadata appears bogus.
Cowardly refusing to proceed any further.
[root@abyss /var/db]#
 

ale

Daemon

Reaction score: 168
Messages: 1,059

robertclemens said:
# portsnap fetch
Looking up portsnap.FreeBSD.org mirrors... 2 mirrors found.
Fetching public key from portsnap1.FreeBSD.org... done.
Fetching snapshot tag from portsnap1.FreeBSD.org... done.
Fetching snapshot metadata... done.
Fetching snapshot generated at Sun Jan 4 19:38:12 EST 2009:
916e4693ea4689b7598778ef6358f1c2705c84aeaf4a79100% of 55 MB 713 kBps 00m00s
Extracting snapshot... done.
Verifying snapshot integrity... done.
Fetching snapshot tag from portsnap1.FreeBSD.org... done.
Fetching snapshot metadata... fetch: http://portsnap1.FreeBSD.org/t/ef1df878b5fba73256d50b9944b5fb8ee1e9d376fec917a60e52af5e02a861b7: Not Found
sha256: ef1df878b5fba73256d50b9944b5fb8ee1e9d376fec917a60e52af5e02a861b7: No such file or directory
[: !=: unexpected operator
mv: rename ef1df878b5fba73256d50b9944b5fb8ee1e9d376fec917a60e52af5e02a861b7 to tINDEX.new: No such file or directory
done.
grep: tINDEX.new: No such file or directory
look: tINDEX.new: No such file or directory

Portsnap metadata appears bogus.
Cowardly refusing to proceed any further.
That's what is was talking about ;)


EDIT:
I run portsnap several times per day and this is the first error message I've got
Code:
Cowardly refusing to downgrade from Mon Jan  5 18:36:54 CET 2009 to Mon Jan  5 14:06:34 CET 2009.
So I updated my clock with ntpdate and I got
Code:
 5 Jan 20:39:17 ntpdate[62802]: step time server 193.204.114.105 offset 812.242543 sec
So it was 812 secs behind!
Very strange!
 

eujedi

New Member


Messages: 14

I have the very same error with tINDEX.new: No such file or directory. I have updated my time and still it gives the same output. What should i do?
 

DutchDaemon

Administrator
Staff member
Administrator
Moderator
Developer

Reaction score: 3,120
Messages: 11,416

Had this on three different servers today. It must be a problem with the portsnap mirrors. In one instance, deleting /var/db/portsnap and running portsnap fetch extract worked, but only after two tries (the first fetch extract produced the same error).
 

ale

Daemon

Reaction score: 168
Messages: 1,059

After my previous post I had no more errors.
I've always used portsnap3.freebsd.org since then.
 

DutchDaemon

Administrator
Staff member
Administrator
Moderator
Developer

Reaction score: 3,120
Messages: 11,416

Maybe a side-effect of 7.1-RELEASE (end of ports freeze, loads of updates today).
 

eujedi

New Member


Messages: 14

My bad! I deleted the /var/db/portsnap and it all magically happened ok!
Sorry for the screaming
 

DutchDaemon

Administrator
Staff member
Administrator
Moderator
Developer

Reaction score: 3,120
Messages: 11,416

It's not your bad. It's obviously a problem @FreeBSD. Or it was, it seems.
 

tangram

Aspiring Daemon

Reaction score: 75
Messages: 523

There's some talk on the mailing list about sub-par performance on portsnap servers because of the new 7.1.

It's just a matter of updating in a couple of days.
 

gammamatrix

New Member


Messages: 3

Portsnap failing in jails - metadata is corrupt

I am unable to get my jails to fetch ports without failing.

The jail host server will fetch without any problems.

Here is the jail error:

Code:
portsnap fetch

Looking up portsnap.FreeBSD.org mirrors... 2 mirrors found.
Fetching snapshot tag from portsnap1.FreeBSD.org... done.
Fetching snapshot metadata... done.
Updating from Tue Dec 30 23:14:16 UTC 2008 to Tue Jan  6 15:30:58 UTC 2009.
Fetching 3 metadata patches. done.
Applying metadata patches... done.
Fetching 3 metadata files... /usr/sbin/portsnap: cannot open 7384b82098e057ca3c7de84565209471909d35edfac4d3d3d07368430f9dfe44.gz: No such file or directory
metadata is corrupt.

Portsnap is not downloading files into:

/var/db/portsnap/files/

Deleting the contents of the directory /var/db/portsnap does not solve the problem.

I have had this problem for months, if not longer. My workaround is to copy the files from the host to the jail. I may just mount the directory to be shared as I do for distfiles.

I have had this problem on 6.X to 7.X. I do not know how long ago it stopped working.

Anybody have any ideas?
 

tangram

Aspiring Daemon

Reaction score: 75
Messages: 523

gammamatrix said:
I am unable to get my jails to fetch ports without failing.

The jail host server will fetch without any problems.

Here is the jail error:

portsnap fetch

Looking up portsnap.FreeBSD.org mirrors... 2 mirrors found.
Fetching snapshot tag from portsnap1.FreeBSD.org... done.
Fetching snapshot metadata... done.
Updating from Tue Dec 30 23:14:16 UTC 2008 to Tue Jan 6 15:30:58 UTC 2009.
Fetching 3 metadata patches. done.
Applying metadata patches... done.
Fetching 3 metadata files... /usr/sbin/portsnap: cannot open 7384b82098e057ca3c7de84565209471909d35edfac4d3d3d07368430f9dfe44.gz: No such file or directory
metadata is corrupt.

Portsnap is not downloading files into:

/var/db/portsnap/files/

Deleting the contents of the directory /var/db/portsnap does not solve the problem.

I have had this problem for months, if not longer. My workaround is to copy the files from the host to the jail. I may just mount the directory to be shared as I do for distfiles.

I have had this problem on 6.X to 7.X. I do not know how long ago it stopped working.

Anybody have any ideas?

Just wait it out. I had same problem last night and a couple hours ago it worked fine again.

Just run

Code:
# freebsd-update upgrade -r 7.1-RELEASE

And follow the steps on the annoucement, http://www.freebsd.org/releases/7.1R/announce.html.

Regarding where freebsd-update places its files... freebsd-update defaults to /var/db/freebsd-update but you can specify another directory through the -d flag. Take a look here for more info, http://linux-bsd-sharing.blogspot.com/2008/12/tip-updating-freebsd-with-freebsd.html.
 

kamikaze

Well-Known Member

Reaction score: 76
Messages: 365

There's been a mail on stable saying that this is due to the strong traffic because of the 7.1 release (mirrors have trouble synchronizing).

It will get better again by itself and a new mirror will be available, soon.
 

gammamatrix

New Member


Messages: 3

Just wait it out. I had same problem last night and a couple hours ago it worked fine again.

This does not have to do with 7.1. This is broken for me in 6.2 and 6.3 for several months.

Portsnap works on the server holding the jails, but not inside the jails.
 

gammamatrix

New Member


Messages: 3

gammamatrix said:
This does not have to do with 7.1. This is broken for me in 6.2 and 6.3 for several months.

Portsnap works on the server holding the jails, but not inside the jails.

To restate myself:

Portsnap is broken for me in jails for 6.2, 6.3, 7.0 and 7.1.

This problem has been around for me for quite some time.
 

francisloco

Member


Messages: 22

how i fix this?

i add to /etc/services

Code:
http            80/tcp          www www-http    # WorldWideWeb HTTP
http            80/udp          www www-http    # HyperText Transfer Protocol
https           443/tcp                         # MCom                       
https           443/udp                         # MCom                       
gss-http        488/tcp                                                      
gss-http        488/udp                                                      
http-alt        8008/tcp                                                     
http-alt        8008/udp                                                     
http-mgmt       280/tcp                         # http-mgmt                  
http-mgmt       280/udp                         # http-mgmt                  
http-rpc-epmap  593/tcp                         # HTTP RPC Ep Map            
http-rpc-epmap  593/udp                         # HTTP RPC Ep Map


then portsnap work again, cuz removing the /var/db/portsnap, the problem back again.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 11,564
Messages: 37,880

gammamatrix said:
To restate myself:

Portsnap is broken for me in jails for 6.2, 6.3, 7.0 and 7.1.
All versions of FreeBSD use the same ports tree.

Great, now I've replied to a year old post x(
 

francisloco

Member


Messages: 22

i havent these lines, so when i add it this work again.

i post it, for someone searching on the same problem, then he can try the fix.
 
Top