Well,
HD is definitely not full, I will maybe try the filesystem check.
will let you know very soon.
On 6/6/05, Dirk Schenkewitz <schenkewitz@docomolab-euro.com> wrote:
> Erik Huelsmann wrote:
> > On 6/4/05, Prateek Srivastava <for.groups@gmail.com> wrote:
> >
> >>Hi Erik,
> >>
> >>Thanks for the reply.
> >>
> >>My machine is new and well configured.
> >>
> >>Do you suspect that some shared libraries have been incorrectly installed?
> >>I tried my best to satisfy all dependancies.
> >>If I can know which one is the problem, I can try ivestigating further.
> >
> >
> > The problem is not with subversion itself, but with the box running
> > the tests: it's not able to produce consistent results while under
> > heavy load, as shown by the errors below:
> >
> > /root/subversion-1.2.0/subversion/clients/cmdline/.libs/lt-svn: error
> > while loading shared libraries:
> > /root/subversion-1.2.0/subversion/libsvn_subr/.libs/libsvn_subr-1.so.0:
> > file too short
> > ----> Here it can't load a library it has successfully loaded hundreds
> > of times before in the same test run
>
> It really *looks like* that, but I have doubts...
> If it really successfully loaded the library *during the test run before*,
> it should be in the memory, unless the machine is so heavily loaded that
> it swapped it out during the test.
> Would it be possible that the library file is corrupted somehow? I mean,
> could it be that "loading" most parts from it succeeds, but a certain
> functions that is needed for the failing test cannot be loaded?
> (Just a wild guess. I'm not sure if loading shared libs could make this
> possible.)
>
> > IOError: [Errno 2] No such file or directory:
> > 'repositories/externals_tests-8/conf/svnserve.conf'
> > ----> Tens of times before, a file by that name has been created successfully
>
> Hmm, could it be possible that the filesystem ran out of space?
>
> > /root/subversion-1.2.0/subversion/clients/cmdline/.libs/lt-svn: error
> > while loading shared libraries:
> > /root/subversion-1.2.0/subversion/libsvn_ra_local/.libs/libsvn_ra_local-1.so.0:
> > file too short
> > ----> Same as the first error
> >
> > /root/subversion-1.2.0/subversion/clients/cmdline/.libs/lt-svn:
> > relocation error:
> > /root/subversion-1.2.0/subversion/libsvn_ra/.libs/libsvn_ra-1.so.0:
> > undefined
> > symbol: svn_ra_dav__init
> > ----> Same as the first error
> >
> >
> >>I have deployed subversion on a production environment. Till now, all
> >>the commands and functions have been working fine. I am just concerned
> >>if it would break at some later stage, or some function misbehaves.
> >
> >
> > Again, it's not subversion, it's the box.
>
> Well... How could one configure a rather new machine to perform "dropouts"
> like these? (<-- Serious question - if it's somehow possible, it could
> hit me soone or later, too.)
> Especially if there are no other problems. Then again, I once had a hard
> disk that had some small areas that were badly damaged while 98% of the
> disk was fine. Unfortunately (or fortunately?) it was the journal area.
>
> My ideas:
> 1. First do a 'df' and look if some filesystem is (nearly) 100% full.
> 2. If that's ok, reboot and do a (forced) filesystem check.
> 3. If ok so far, run a memory test.
> 4. If still nothing shows up, try to build an older subversion version.
> 5. If that works, try again with subversion 1.2.
>
> Just my 2 cents. Best regards
> Dirk
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 7 06:20:23 2005