On Wed, 12 Nov 2008 17:49:09 +0200, LITNET wrote in message <[🔎] 491AFAF5.6080903@litnet.lt>: > Hello, > > There is an error updating mirrors via > http://cgi.debian.org/cgi-bin/submit_mirror.pl script. Script produces > this output: > > The following entries were submitted: > > Submission-Type: update > > Site: ftp.litnet.lt > Type: leaf > Archive-architecture: ALL alpha amd64 arm armel hppa hurd-i386 i386 > ia64 m68k mips mipsel powerpc s390 sparc > Archive-ftp: /debian/ > Archive-http: /debian/ > Archive-rsync: debian/ > CDImage-ftp: /debian-cd/ > CDImage-http: /debian-cd/ > CDImage-rsync: debian-cd/ > Volatile-ftp: /debian-volatile/ > Volatile-http: /debian-volatile/ > > A proper project/trace directory was not found on the HTTP server > (under /debian-volatile/). > > The error message returned was: 404 Not Found > > If you don't understand this error message, please contact us. > > Entry not submitted! > > > >From the logs I see, that script searches > >"volatile-master.debian.net": > 70.103.162.29 - - [12/Nov/2008:17:39:57 +0200] "GET > /debian-volatile/project/trace/volatile-master.debian.net HTTP/1.1" > 404 254 "-" "libwww-perl/5.805" > > But /debian-volatile/project/trace/ looks like this: > nierka@ameba:~$ ls -alh /disk/debian-volatile/project/trace/ > total 8.0K > drwxrwxr-x 2 root root 136 2008-11-01 02:48 . > drwxrwxr-x 3 root root 112 2005-12-16 21:33 .. > -rw-rw-r-- 1 root root 29 2008-11-12 03:32 ameba.sc-uni.ktu.lt > -rw-r--r-- 1 root root 29 2008-11-12 01:07 volatile-master.debian.org > nierka@ameba:~$ > > I cannot submit update on mirror ameba.sc-uni.ktu.lt. > -- > Sincerely > LITNET FTP admin > Nerijus Kislauskas ..fwiw, output of ' dig ameba.sc-uni.ktu.lt ', ' lynx -dump http://ameba.sc-uni.ktu.lt/ ' and ' lynx -dump http://ameba.sc-uni.ktu.lt/debian ' attached: ll lt-mir && md5sum lt-mir -rw-r--r-- 1 arnt arnt 6548 Nov 12 20:14 lt-mir 0e94668971c830cf254fa7dbafcd8ec9 lt-mir -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case.
Attachment:
lt-mir
Description: Binary data