1 |
Dave Nebinger <dnebinger <at> joat.com> writes: |
2 |
|
3 |
> |
4 |
> > I recently set up an internal server for rsync and distfile distribution. |
5 |
> > How do I check to ensure that this internal server actually was successful |
6 |
> > at downloading the rsync files and the appropriate distfiles for the other |
7 |
> > sytems? |
8 |
> |
9 |
> /usr/portage/metadata/timestamp contains the timestamp for when the sync was |
10 |
> completed. |
11 |
> |
12 |
Ahhh that's it: |
13 |
# cat /usr/portage/metadata/timestamp |
14 |
Tue Jul 12 13:06:52 UTC 2005 |
15 |
# date |
16 |
Wed Jul 13 12:05:26 UTC 2005 |
17 |
|
18 |
The clock (hw and OS) were off, by about25 minutes but that has |
19 |
been correct now. /etc/crontab was set for 1:30 |
20 |
30 1 * * * root emerge sync |
21 |
|
22 |
> > PROBLEM? |
23 |
> > I manually ran 'emerge -uDp world' today on both a client and the |
24 |
> > sever. The client updated a few files, the server returned nothing to |
25 |
> > update. |
26 |
> > I kept another p4 system using rsync and downloading the distfiles |
27 |
> > separate. |
28 |
> |
29 |
> Since the server is the local rsync mirror it must do it's emerge --sync |
30 |
> first. After it has completed (note: not during the run), the client(s) can |
31 |
> emerge --sync. |
32 |
> |
33 |
> > emerge -uDp world shows this file (among others) on the P4 system using |
34 |
> > the old external update method: |
35 |
> > [ebuild NS ] sys-kernel/gentoo-sources-2.6.12-r5 |
36 |
> > |
37 |
> > The new internal-AMD rsync/distfile server, issueing |
38 |
> > 'emerge -s gentoo-sources' shows: |
39 |
> > sys-kernel/gentoo-sources |
40 |
> > Latest version available: 2.6.12-r4 |
41 |
> > Latest version installed: 2.6.12-r4 |
42 |
> > |
43 |
> > Is this evidence that the nightly updates, are not working on the |
44 |
> > internal server? |
45 |
> |
46 |
> No, it is merely an indication that at some point between the server's sync |
47 |
> and the older sync that -r5 of gentoo sources was released. My systems, as |
48 |
> of last night around midnight thought only -r4 was available. Just now I |
49 |
> ran emerge --sync on the server and it now sees that -r5 is available. |
50 |
> |
51 |
> It's strictly a timing issue. |
52 |
|
53 |
Well now I'm starting to 'get it'. Before when I ran rsync manually, |
54 |
it did not update (rsync was launched last night (EST), so |
55 |
I got some error message about not being available or something |
56 |
like that. Now I just ran 'emerge syncc' maually on the server |
57 |
machine and it did update the rsync files (portage cache). |
58 |
On the internal server |
59 |
emerge -uDp world now does not reveal any new files to update... |
60 |
|
61 |
> |
62 |
> > Is there a simple test to determine if the updates are working |
63 |
> > on the rsync and distfiles? |
64 |
> |
65 |
> Sure. New packages are released every day. I can't remember a single day |
66 |
> in the last month where emerge -uDp reported no packages to update. |
67 |
> |
68 |
> So if you run a few days and constantly see emerge -uDp reporting no |
69 |
> packages, there's probably a sync problem. |
70 |
|
71 |
Well 2 things. |
72 |
|
73 |
I'm going to implement your scripts now. And I shall have patiences |
74 |
for a few days to see how the updates proceed on the internal server |
75 |
and the clients using the internal server. Checking against the |
76 |
internal clients still using remote servers for rsync and distfile |
77 |
updates.... |
78 |
|
79 |
Thanks, |
80 |
|
81 |
James |
82 |
|
83 |
|
84 |
|
85 |
|
86 |
|
87 |
|
88 |
-- |
89 |
gentoo-user@g.o mailing list |