Yeah, it would have been lucky if you had a log message, but I'm not
surprised there wasn't one.
If the app works fine on another computer, and your failure is a system
crash, not an app crash, then you're looking at a lower-level problem, and
all that that entails:
1) Windows problem (they still happen)
2) Conflict with another app (antivirus?)
3) Driver problem (and you have a lot of drivers; disk, mobo, network,
etc)
4) Hardware problems, i.e. heat
5) power supply
6) RAM
7) HD
8) NIC
9) motherboard
10) CPU (yes, even a CPU can give you intermittent or load-related
failures)
11) Etc. This is just off the top of my head.
If you have a test that reliably reproduces a problem, you're in great
shape. If you're in a hurry, you can just give up and switch to a machine
that works. If you want to fix the machine you have, that's easy too, if a
bit more time-consuming. Prioritize the list of possible problems in order
of likelihood and start swapping, eliminating them one by one, and you
will find it eventually.
On Fri, 13 May 2005, Ayende Rahien wrote:
> I tried it on my laptop, and it got to 4800 before I got tired of it.
> However, there isn't anything in the logs of the computer that gives the
> error.
>
> Beyond that, can you suggest a reason why sometimes (on multiply computers),
> the repository would stop responding, causing builds failures?
>
> -----Original Message-----
> From: David Wood [mailto:obsidian@panix.com]
> Sent: Friday, May 13, 2005 3:48 PM
> To: Mark Parker
> Cc: Ayende Rahien; users@subversion.tigris.org
> Subject: Re: Denial of service using SVNServe on WinXp
>
> Agreed.
>
> Two suggestions:
>
> 1) Try this on another machine, preferably a different model/manufacturer.
>
> 2) Check your system event log; see if you're seeing any
> SMART/network/system/etc. type errors. Probably not, but you never know.
>
> On Fri, 13 May 2005, Mark Parker wrote:
>
>> In general, userspace programs can't create the sort of problems you're
>> seeing ("hard" lockups). It it almost certainly a problem with the kernel,
> a
>> driver, or your hardware.
>>
>> I'm guessing you have a bad nic, or a bad driver for it. It's also
> possible
>> you have bad memory or something else such as a processor (fan working?)
> or
>> chipset problem.
>>
>> As an example, Blizzard's recent online game World of Warcraft uses a
>> bittorrent system to distribute patches. For some reason it exercises NICs
>
>> enough to bring out bugs in some drivers. Specifically, some netgear cards
>
>> and some linksys cards with certain driver versions will exibit the sort
> of
>> behavior you're seeing.
>>
>> Mark
>>
>> Ayende Rahien wrote:
>>> Here is the scenario, I've a WinXP Pro computer that I used to run SVN &
>>> CruiseControl.Net. I started to get a lot of broken build emails, all of
>>> them pointing the blame to SVN connectivity (the message was: "the target
>
>>> machine actively refused the connection"). The CC.Net & SVN are on the
> same
>>> machine.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 13 22:59:32 2005