Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
HOWTO:Download Cache for your LAN-Http-Replicator (ver 3.0)
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3 ... 18, 19, 20 ... 22, 23, 24  Next  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
golding
Apprentice
Apprentice


Joined: 07 Jun 2005
Posts: 230
Location: Adelaide / South Australia

PostPosted: Sat May 06, 2006 2:55 am    Post subject: Reply with quote

flybynite,
I installed http-replicator on the server about three months ago and it has worked as a cache perfectly. The problem I am having is getting it to start on boot. If I check rc-status after bootup, http-replicator is stopped, however, if I then start it via the command line;
Code:
/etc/init.d/http-replicator start
is stays up until I close down the server.

I'm having the same problem Haakon had (I think) except my /tmp permissions (0777 +t) are fine and if I start it from the command line using (note --user portage)
Code:
/usr/bin/http-replicator -s -f --pid /var/run/http-replicator.pid --daemon --dir /var/cache/http-replicator --user portage --alias /usr/portage/packages/All:All --log /var/log/http-replicator.log --debug --ip 192.168.99.* --port 8080
it works fine.

I have done everything Haakon did, but still no joy on getting http-replicator to start properly on boot.

Any other ideas?
_________________
Regards, Robert

..... Some people can tell what time it is by looking at the sun, but I have never been able to make out the numbers.
Back to top
View user's profile Send private message
flybynite
l33t
l33t


Joined: 06 Dec 2002
Posts: 620

PostPosted: Sun May 07, 2006 3:11 am    Post subject: Reply with quote

golding wrote:
if I then start it via the command line;
Code:
/etc/init.d/http-replicator start
is stays up until I close down the server.


This is the same way replicator is started by the init scripts.

golding wrote:
if I start it from the command line using (note --user portage)
Code:
/usr/bin/http-replicator -s -f --pid /var/run/http-replicator.pid --daemon --dir /var/cache/http-replicator --user portage --alias /usr/portage/packages/All:All --log /var/log/http-replicator.log --debug --ip 192.168.99.* --port 8080
it works fine.


So using both these methods it works for you, so it's not the same problem.


Set the debug option and start it up so it will fail. Are there messages in replicators log or the system log?

Show me this:
Code:

rc-update show
Back to top
View user's profile Send private message
golding
Apprentice
Apprentice


Joined: 07 Jun 2005
Posts: 230
Location: Adelaide / South Australia

PostPosted: Sun May 07, 2006 10:49 am    Post subject: Reply with quote

flybynite wrote:
Are there messages in replicators log or the system log?
The boot screen shows it starting OK. No errors listed in the system log.
The following is from when I last rebooted the machine yesterday
Code:
06 May 2006 09:38:17 INFO: HttpReplicator terminated
06 May 2006 12:05:58 INFO: HttpReplicator started
06 May 2006 12:19:02 INFO: HttpReplicator started
07 May 2006 09:08:00 STAT: HttpClient 1 bound to 192.168.99.1
About a quarter hour after I rebooted I checked with rc-status, found it "Stopped" so ran it with
Quote:
one rob # /etc/init.d/http-replicator restart
* starting http-replicator ... [OK]
As you can see, it shows when I shut down in the morning, rebooted at lunch and restarted it after my cuppa, but, nothing to show it stopping in between the two starts.

flybynite wrote:
Set the debug option and start it up so it will fail. Are there messages in replicators log or the system log?
OK, is that a switch, or do I need to re-emerge the package


flybynite wrote:
Show me this:
Code:

rc-update show
Right here
Code:
one rob # rc-update show
           alsasound |      default
            bootmisc | boot
             checkfs | boot
           checkroot | boot
               clock | boot
         consolefont | boot
               cupsd |      default
                dbus |      default
            gkrellmd |      default
                 gpm |      default
                hald |      default
            hostname | boot
             hotplug | boot
     http-replicator |      default
            iptables |      default
             keymaps | boot
          lm_sensors | boot
               local |      default nonetwork
          localmount | boot
             modules | boot
            net.eth0 |      default
              net.lo | boot
            netmount |      default
                 nfs |      default
          ntp-client |      default
                ntpd |      default
             numlock |      default
             portmap |      default
           rmnologin | boot
              rsyncd |      default
           syslog-ng |      default
             urandom | boot
                 xdm |      default
                 xfs |      default
              xinetd |      default

_________________
Regards, Robert

..... Some people can tell what time it is by looking at the sun, but I have never been able to make out the numbers.
Back to top
View user's profile Send private message
flybynite
l33t
l33t


Joined: 06 Dec 2002
Posts: 620

PostPosted: Sun May 07, 2006 9:12 pm    Post subject: Reply with quote

golding wrote:
About a quarter hour after I rebooted I checked with rc-status, found it "Stopped"



You would only get the status "stopped" if replicator was shutdown with the init scripts. If replicator died, you would get an error message when you tried to restart it with the 'restart' or 'start' command.

Here I check the status, start, kill replicator, then try to start or restart. Notice the errors.


Code:

gate1 ~ # /etc/init.d/http-replicator status
 * status:  stopped
gate1 ~ # /etc/init.d/http-replicator start
 * Starting Http-Replicator ...                                                                                                                       [ ok ]
gate1 ~ # killall http-replicator
gate1 ~ # /etc/init.d/http-replicator status
 * status:  started
gate1 ~ # /etc/init.d/http-replicator start
 * WARNING:  "http-replicator" has already been started.
gate1 ~ # /etc/init.d/http-replicator restart
 * Stopping Http-Replicator ...
No http-replicator found running; none killed.                                                                                                        [ ok ]
 * Starting Http-Replicator ...                                                                                                                       [ ok ]




I suspect replicator is being stopped by the init scripts. Maybe because you start and stop your network?

replicator "needs net" and if you stop your net, replicator will stop also.

Code:

gate1 ~ # /etc/init.d/net.eth0 stop
 * Stopping Http-Replicator ...                                                                                                                       [ ok ]
 * Unmounting network filesystems ...                                                                                                                 [ ok ]
 * Stopping ntpd ...                                                                                                                                  [ ok ]
 * Stopping sshd ...                                                                                                                                  [ ok ]
 * Stopping eth0
 *   Bringing down eth0
 *     Stopping dhcpcd on eth0 ...                                                                                                                    [ ok ]
 *     Shutting down eth0 ...                                                                                                                         [ ok ]



Do you use the init scripts to bring your network up or down?
Back to top
View user's profile Send private message
golding
Apprentice
Apprentice


Joined: 07 Jun 2005
Posts: 230
Location: Adelaide / South Australia

PostPosted: Mon May 08, 2006 1:28 am    Post subject: Reply with quote

flybynite wrote:
You would only get the status "stopped" if replicator was shutdown with the init scripts.
Agreed, but what script?
flybynite wrote:
I suspect replicator is being stopped by the init scripts. Maybe because you start and stop your network?
The network comes up, then stays up. Pinging the other machines from boot keeps going, before, during and after whatever is going on with the replicator.
flybynite wrote:
Do you use the init scripts to bring your network up or down?
I startup the server, when it is up, I then start the clients (clients need the server up first for nfsmount of 'home'). All of it is done via the init scripts.

I am not known for being any good at fault finding. I am more a "fudger" than expert, so this morning I thought I would try something different.
I started up the server, then clients, as I usually do, then ran a script to ping the clients from the server. I also ran a script to run "rc-status" every 30 seconds so I could see when (and if) http-replicator stopped. From the clients I ran emerge to download a large set of files from the server.

I did this in case there was something closing the replicator down from non use, a sort of service automounter? It seems I was wrong as it still stopped, even when it was up and running in use.

What happened is that it all worked for seventeen minutes, then 'rc-status' reported http-replicator "Stopped" and the clients showed connection denied for emerge at the same time. During all this the ping and nfs maintained their connections, so I can safely say the network stayed up.

I do not know what caused http-replicator to stop at seventeen minutes, the log still only shows termination from last night and start for this morning. When I restarted the replicator, the log only showed an additional 'start', still no entry for the termination at seventeen minutes. There was also no error showing the replicator was already stopped when I restarted it.

I re-emerged http-replicator, net-tools, python, nfs, nfs-tools, ntp, portmap, ... etc, last night in case a bug in the install was the cause.
_________________
Regards, Robert

..... Some people can tell what time it is by looking at the sun, but I have never been able to make out the numbers.
Back to top
View user's profile Send private message
flybynite
l33t
l33t


Joined: 06 Dec 2002
Posts: 620

PostPosted: Mon May 08, 2006 4:42 am    Post subject: Reply with quote

Ok, hmm....

Debug is in /etc/conf.d/http-replicator, remove the # before this line:
Code:

## Make the log messages extra verbose for debugging.
DAEMON_OPTS="$DAEMON_OPTS --debug"


Restart replicator and try the test again. Should see some more output.
Back to top
View user's profile Send private message
wa1gon
n00b
n00b


Joined: 21 Nov 2005
Posts: 1
Location: Mason, NH

PostPosted: Mon May 08, 2006 9:33 pm    Post subject: Failed MD5 verification Reply with quote

:cry: I just installed http-replicator and I have started to have to get the message:


!!! Digest verification Failed:
!!! /usr/portage/distfiles/bash-3.1.tar.gz
!!! Reason: Failed on MD5 verification

on just about any package I try to install. Did I miss something?

help

thanks

Darryl -- de WA1GON
Back to top
View user's profile Send private message
golding
Apprentice
Apprentice


Joined: 07 Jun 2005
Posts: 230
Location: Adelaide / South Australia

PostPosted: Tue May 09, 2006 1:07 am    Post subject: Reply with quote

flybynite wrote:
Ok, hmm....

Debug is in /etc/conf.d/http-replicator, remove the # before this line:
Code:

## Make the log messages extra verbose for debugging.
DAEMON_OPTS="$DAEMON_OPTS --debug"


Restart replicator and try the test again. Should see some more output.


OK, I activated debug and restarted.

Now the behaviour is getting really weird. It is showing [started] but not allowing connections, then showing [stopped] from boot, then [started] for awhile and changing to [stopped] ... you get the idea? During all this it only shows normal output to the log file, no extra information :-(

Oh well, I think something is messed up with my total Gentoo install, maybe a package doing something totally unrelated but using net in some way, and is manifesting itself through the replicator (weirder things do happen), so until I have re-installed the entire Gentoo from scratch again I'll let this one lie. Probably in a month os so, I don't feel so masochistic at the moment :?

Until then I'll just have to restart the replicator when needed. After all, it seems this is only happening on my systems, not any others, otherwise I reckon we would have had a couple of "me too" posts.

Thankyou for your time and effort flybynite :-)
_________________
Regards, Robert

..... Some people can tell what time it is by looking at the sun, but I have never been able to make out the numbers.
Back to top
View user's profile Send private message
golding
Apprentice
Apprentice


Joined: 07 Jun 2005
Posts: 230
Location: Adelaide / South Australia

PostPosted: Thu May 11, 2006 2:28 am    Post subject: Reply with quote

Progress! ... sort of :?

I have been keeping tabs on the replicator behaviour for the last two days and noticed something different.

If I startup and work the server without root having been logged in, it all works properly. As soon as I login to the server as root, either by su or in a console, the replicator stops. Then I restart it from command line as root, thereafter it keeps working fine.

I hadn't noticed the correlation between this and the replicator before as I wasn't working without logging into root fairly soon for various reasons. The seventeen minute delay before was when I first su'd to do something. The varying behaviour was for the same reason, if I su'd straight away, replicator stopped then, if I did other things first, then su'd, the replicator stopped then. Even the scripts I ran to test it were ran from a user account, so I didn't see it then either.

I've never used ssh, so I don't know if this would happen if I logged into the server via ssh as root. I also haven't tried sudo [command] as I never really used it before (much easier to su, then run whatever you need to).

I cannot see anything in profile or bashrc that could cause a problem, they are stock standard excepting an alias for ls --color for root.

Sooo .. any other ideas?

_________________
Regards, Robert

..... Some people can tell what time it is by looking at the sun, but I have never been able to make out the numbers.
Back to top
View user's profile Send private message
Conditional_Zenith
Apprentice
Apprentice


Joined: 22 Sep 2004
Posts: 150
Location: Australia

PostPosted: Sat May 27, 2006 6:16 am    Post subject: Reply with quote

Are there any solutions which use apache to do this? I already use apache anyway, and I would like to avoid having 2 different http servers running on my box.
Back to top
View user's profile Send private message
flybynite
l33t
l33t


Joined: 06 Dec 2002
Posts: 620

PostPosted: Sun May 28, 2006 4:16 pm    Post subject: Reply with quote

Conditional_Zenith wrote:
Are there any solutions which use apache to do this?


Yes, I originally used apache!!

See my HOWTO: tsp-cache - Streaming Distfile Cache for LAN Use for tsp cache which I wrote back in 2003!!. ( I can't believe it's still there! )


It is tailor made for someone already running apache, but apache has some serious limitations as a distfile server. http-replicator is much more featured and powerful.

The download link in the howto is dead. If your still interested we can find a way to get it to ya, it's only 11kb!
Back to top
View user's profile Send private message
Scen
Retired Dev
Retired Dev


Joined: 29 Jul 2003
Posts: 2470
Location: Padova, Italy

PostPosted: Tue May 30, 2006 9:03 am    Post subject: Reply with quote

Hello to everybody!

I still have the "service start" problem of http-replicator, that is the boot process shows "Starting Http-Replicator [OK]" but, when i check the existence of the http-replicator process, it doesn't exists.
Indeed, if i restart the service, it starts without problems with the following message
Code:

# /etc/init.d/http-replicator restart
 * Stopping Http-Replicator ...
No http-replicator found running; none killed.                            [ ok ]
 * Starting Http-Replicator ...                                           [ ok ]
#

This problem appeared with the latest stable version of the 2.6 kernel (>= 2.6.13, maybe) , while with a 2.4 kernel (or a early 2.6) the service starts fine.

If i don't put http-replicator service in "default" runlevel and, after the system have booted, i run the command
Code:

/etc/init.d/http-replicator start

the service starts fine.

I have tried to add "--debug" and "--intolerant" options in /etc/conf.d/http-replicator but the log doesn't have useful informations, and the runscript seems to start the service without problems.

flybynite, i'm in your hands! :roll:

p.s. sorry for my bad english!
_________________
I was born in a deep forest/I wish I could live here all my life/I am made from stones and roots/My home, these woods and roads
All my life I loved this sound/Of the woods all around/Eagles flies where the winds blows free
Journey is my destiny
Back to top
View user's profile Send private message
golding
Apprentice
Apprentice


Joined: 07 Jun 2005
Posts: 230
Location: Adelaide / South Australia

PostPosted: Tue May 30, 2006 2:39 pm    Post subject: Reply with quote

I shifted http-replicator to one of my machines running stable (x86) only, and it now works fine. All the problems I had with it on my server have disappeared.

Maybe this is to do with using ~x86?



edit (1) - changed sentence to read correctly
_________________
Regards, Robert

..... Some people can tell what time it is by looking at the sun, but I have never been able to make out the numbers.
Back to top
View user's profile Send private message
flybynite
l33t
l33t


Joined: 06 Dec 2002
Posts: 620

PostPosted: Wed May 31, 2006 9:25 pm    Post subject: Reply with quote

golding wrote:

Maybe this is to do with using ~x86?



Could be. Could you make some small tests to see if you could narrow it down to which packages.... Replicator should only be interested in python or kernel versions. Is python or kernel different on the two boxes?

Although I still think something is changeing when you login with ssh. Maybe ssh is doing some port forwarding or other trickery for you?
Back to top
View user's profile Send private message
flybynite
l33t
l33t


Joined: 06 Dec 2002
Posts: 620

PostPosted: Wed May 31, 2006 9:36 pm    Post subject: Reply with quote

Scen wrote:

I still have the "service start" problem of http-replicator, that is the boot process shows "Starting Http-Replicator [OK]" but, when i check the existence of the http-replicator process, it doesn't exists.



The last person with this error had incorrect permissions in the temp dir. Show me

Code:

ls -l /


If that looks like

Code:

drwxrwxrwt  19 root root  1384 May 31 16:12 tmp



Then follow my posts with Haakon here:
https://forums.gentoo.org/viewtopic-t-173226-postdays-0-postorder-asc-start-416.html

Don't worry about his replies, just run the tests I ask him. I should make this into a FAQ someday so I don't have to repeat it too often...
Back to top
View user's profile Send private message
Havin_it
Veteran
Veteran


Joined: 17 Jul 2005
Posts: 1164
Location: Edinburgh, UK

PostPosted: Thu Jun 01, 2006 11:18 am    Post subject: Reply with quote

Hi all :)

I've used http-replicator with no issues for a few months now, but suddenly I'm getting a problem with repcacheman. When I run it, it parses the DISTDIR, finds all the ebuilds, but then hangs interminably (well, 10min and over) on the line "Extracting the checksums...."

Any idea what's doing this? I've just done an emerge -uD world, but didn't take note of what packages were merged. I don't think there's been an update to http-replicator for a while, though I re-emerged it just in case the install was b0rked, but that's made no difference.

Nothing alarming in the logs either. What else can I try?

EDIT: Never mind, it completed eventually, just took a really long time. Still curious as to why though...
Back to top
View user's profile Send private message
flybynite
l33t
l33t


Joined: 06 Dec 2002
Posts: 620

PostPosted: Sat Jun 03, 2006 10:47 pm    Post subject: Reply with quote

Havin_it wrote:
Hi all :)
EDIT: Never mind, it completed eventually, just took a really long time. Still curious as to why though...


You might be having a problem with your setup or your selected http mirrors. This might cause ALL your downloads to come from ftp and slow repcacheman way down. repcacheman only does the full blown md5sum check on the rare file that isn't available in GENTOO_MIRRORS in your /etc/make.conf. Make sure you have a full set of healthy http mirrors in there.

I should also add that portage is disk limited during this check, if another disk intensive process is running at the same time, they both will slow way down.

However, to answer your question.

repcacheman uses portage databse functions to read every single ebuild in the whole portage tree. This takes time. This will take more time as the tree grows. Also portage isn't optimized to do the database lookups repcacheman does. Repcacheman could really use its own database to optimize the queries, but I haven't had any other complaints about the speed since 99.9% of the files should be on an http mirror and repcacheman should only rarely have to do the full blown md5sum check.

Portage is under heavy development now, and portage 2.1 + is much faster due to structural changes and optimizations. Hopefully that will translate to a faster repcacheman also.

I've noticed a slowdown in stable portage. I believe either portage 2.0 is buckling under the load or maybe is slowing down because of the changes being made behind the scenes for portage 2.1, which isn't far from being released as stable, but is very different in the database department.


You may not need to run repcachman as often if you are finding the run time troublesome. Once replicator is installed and running healthy, repcacheman only serves to transfer a couple of files that may have been only available on ftp to replicators cache. If you don't run repcachman, the worst that will happen is that individual boxes may rarely have to ftp one or two files themselves. This might mean that only 99.9% of the files are downloaded once and cached, instead of 100%. If your running hundreds of clients and paying per MB downloaded that might be unacceptable, otherwise running repcacheman less often could be for you.
Back to top
View user's profile Send private message
hpeters
n00b
n00b


Joined: 26 Sep 2003
Posts: 68

PostPosted: Wed Jun 07, 2006 2:22 am    Post subject: Problem with http-replicator on the server.. Reply with quote

I am having a problem where http-replicator never even receives the request from portage when emerging a file.
This only happens on the server ( the machine running http-replicator ). All the other computers on the lan work great.
Every thing is set up correctly the http_proxy variable is set, gentoo mirrors is set. But when i emerge a file portage connects directly to the portage mirror and never even attempts to connect to htp-replicator.
I am using http-replicator 3.0 and the latest ~x86 version of portage. I have tried with the "stable" version of portage and it didn't work either.

Any ideas ?
Back to top
View user's profile Send private message
hpeters
n00b
n00b


Joined: 26 Sep 2003
Posts: 68

PostPosted: Wed Jun 07, 2006 4:29 pm    Post subject: Reply with quote

Ok i found the problem wgetrc located at /etc/wget/wgetrc had the configuration variable use_proxy=off set.
Commenting that out fixed the problem. How it got set in the first place i don't know. I have never modified that config file in my life.

Harley
Back to top
View user's profile Send private message
phsdv
Guru
Guru


Joined: 13 Mar 2005
Posts: 372
Location: Europe

PostPosted: Sat Jun 17, 2006 9:51 am    Post subject: Reply with quote

Since a while, probably since unmaksing portage2.1, I have some issues with repcacheman. see code below
Code:
# /usr/bin/repcacheman

Replicator's cache directory: /var/cache/http-replicator/
Portage's DISTDIR: /usr/portage/distfiles/

Comparing directories....
Done!

Deleting duplicate file(s) in /usr/portage/distfiles/
http-replicator_3.0.tar.gz
Done!

New files in DISTDIR:
pvr_2.0.24.23035.zip
... some more files ...
gcc-3.4.5-ssp-1.0.tar.bz2

Checking authenticity and integrity of new files...
Searching for ebuilds...
Done!

Found 23941 ebuilds.

Extracting the checksums....
Traceback (most recent call last):
  File "/usr/bin/repcacheman.py", line 162, in ?
    digestpath = os.path.dirname(digestpath)+"/files/digest-"+pv
  File "/usr/lib/python2.4/posixpath.py", line 119, in dirname
    return split(p)[0]
  File "/usr/lib/python2.4/posixpath.py", line 77, in split
    i = p.rfind('/') + 1
AttributeError: 'NoneType' object has no attribute 'rfind'
Is this a buf from repcacheman or from my system? Does anyone know how to fix this?

[edit]I added some print statements and found why it stops:
Code:
pv kuroo-0.80.2
digestpath: /usr/portage/app-portage/kuroo/kuroo-0.80.2.ebuild
digestpath: /usr/portage/app-portage/kuroo/files/digest-kuroo-0.80.2
pv kuroo8-svn-0_beta1
digestpath: None
Traceback (most recent call last):
  File "/usr/bin/repcacheman.py", line 163, in ?
    digestpath = os.path.dirname(digestpath)+"/files/digest-"+pv
  File "/usr/lib/python2.4/posixpath.py", line 119, in dirname
    return split(p)[0]
  File "/usr/lib/python2.4/posixpath.py", line 77, in split
    i = p.rfind('/') + 1
AttributeError: 'NoneType' object has no attribute 'rfind'
I will remove this package. and I expect it to work again.[/edit]
Back to top
View user's profile Send private message
flybynite
l33t
l33t


Joined: 06 Dec 2002
Posts: 620

PostPosted: Sun Jun 18, 2006 4:31 am    Post subject: Reply with quote

phsdv wrote:
Since a while, probably since unmaksing portage2.1, I have some issues with repcacheman



This comes up from time to time. repcacheman just uses the portage API to access the data so when portage is updated, repcacheman is updated also. Of course someday the portage API might change, but since it still works for me I don't think that has happened yet :-)


The problem your having usually means an illegal/missing/invalid entry is in the portage database. A gentoo dev will fix this in a few hours or maybe a day. repcacheman will probably work fine after your next sync.

Of course, you might have put the bad data in the database yourself. Do you have any portage overlays?

If this error still happens after your next sync, temporarily remove any overlay's you have to see if one of them is the cause.


[edit] Seems you've found the offending ebuild. If it is still broke after your next sync file a bug to the maintainer of that ebuild....
Back to top
View user's profile Send private message
phsdv
Guru
Guru


Joined: 13 Mar 2005
Posts: 372
Location: Europe

PostPosted: Sun Jun 18, 2006 8:07 am    Post subject: Reply with quote

flybynite wrote:
[edit] Seems you've found the offending ebuild. If it is still broke after your next sync file a bug to the maintainer of that ebuild....
:oops: the offending ebuild maker was found, the ebuild was in a local overlay which I had made myself :oops:
Back to top
View user's profile Send private message
bodelicious
n00b
n00b


Joined: 15 Jun 2006
Posts: 6

PostPosted: Thu Jun 29, 2006 3:18 am    Post subject: emerge is unable to download files Reply with quote

i can ping a server
dhcpcd is running
but when i want to download some packages through emerge it hangs saying > " ...connected. HTTP request sent, awaiting response... No data received."
and eventually
"Giving up."

i didn't find any answer to your old post but i assume you got it fixed

could you help me to solve this problem please?

thx!


xkb wrote:
I get the following error on the machine running the proxy:

Code:

Resolving myhostname.net... someip
Connecting to myhostname.net[someip]:8080... connected.
Proxy request sent, awaiting response...
10:16:22 ERROR -1: No data received.


Any ideas whats causing this? I followed the howto.

The proxy works fine for the client machines.

Code:

>>> Downloading http://distro.ibiblio.org/pub/Linux/distributions/gentoo/distfiles/portage-2.0.50-r9.tar.bz2
--10:20:56--  http://distro.ibiblio.org/pub/Linux/distributions/gentoo/distfiles/portage-2.0.50-r9.tar.bz2
           => `/usr/portage/distfiles/portage-2.0.50-r9.tar.bz2'
Resolving mydomain.net... done.
Connecting to mydomain.net[someip]:8080... connected.
Proxy request sent, awaiting response... 404 Not Found
10:20:57 ERROR 404: Not Found.
 
>>> Downloading http://gentoo.twobit.net/portage/portage-2.0.50-r9.tar.bz2
--10:20:57--  http://gentoo.twobit.net/portage/portage-2.0.50-r9.tar.bz2
           => `/usr/portage/distfiles/portage-2.0.50-r9.tar.bz2'
Resolving mydomain.net... done.
Connecting to mydomain.net[someip]:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 222,044 [application/x-tar]

After this it appears in /var/cache/http-replicator
Back to top
View user's profile Send private message
flybynite
l33t
l33t


Joined: 06 Dec 2002
Posts: 620

PostPosted: Sat Jul 01, 2006 4:13 am    Post subject: Re: emerge is unable to download files Reply with quote

First, check your config file on the server, since other clients work fine, most likely the server /etc/make.conf file has errors.


I need to make a troubleshooting FAQ soon, but then try to follow this exchange between haakon and I. You may not have the same problem, but the troubleshooting steps are the same.

Perform the steps I have haakon do to start the troubleshooting.

https://forums.gentoo.org/viewtopic-t-173226-postdays-0-postorder-asc-start-413.html
Back to top
View user's profile Send private message
Kobboi
l33t
l33t


Joined: 29 Jul 2005
Posts: 661
Location: Belgium

PostPosted: Tue Aug 01, 2006 8:30 pm    Post subject: Reply with quote

Forgive me for not reading the whole thread before asking my questions :oops:
(If you really hold this against me, replies like "it's in the thread" are allowed)

- What happens if client 1 wants a (huge) file and client 2 as well, requesting it before it has been completely downloaded by http-replicator? client 2 gets a partial (invalid) file? no all that bad in an emerge context, but i'd like to know.

- I often do an emerge -avuDf (=complete update, but fetch only), just to have the necessary files already in place for when eventually do update. One package (ivtv) keeps downloading two files over ftp, although they are in the cache. What is the reason for this and how do I "solve" this?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Goto page Previous  1, 2, 3 ... 18, 19, 20 ... 22, 23, 24  Next
Page 19 of 24

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum