svn malfunction (Re: [immodule-qt] Porting to Qt4)

[YamaKen]

I've sent the request.

> To: Daniel Stone <daniel at freedesktop.org>, sitewranglers at freedesktop.org
> Subject: Please restart apache2 to free permanently locked svn mutex
> From: YamaKen <yamaken at bp.iij4u.or.jp>
> Date: Thu, 02 Sep 2004 00:30:15 +0900
> 
> Hello admins, please help our project.
> 
> I'm a developer of project "immodule for Qt" on fdo, and we are
> suffering strange deadlock problem on the svn repository. Please
> restart apache2 to free the permanently locked svn mutex.
> 
> Problem details:
> 
> Since 22 Aug, we can't access our svn repository by any protocol
> and any commands. All trial such as svn update or svn log are
> waiting forever, so I investigated what is the problem. After
> some test and debugging with gdb and strace, I've found a mapped
> mutex on a meta-information file (__db.001) is always
> locked. This disables all operations on Berkeley DB layer such
> as deadlock-detection by db_deadlock. The db_deadlock command is
> waiting forever as same as svn commands.
> 
> I'm guessing that one of apache2 process is permanently locking
> the mutex. Only our repository shows following strange result by
> fuser. I think that killing the processes is required for
> recovery. Please restart apache2 to kill them.
> 
> $ fuser /svn/immqt/db/*
>                      USER        PID ACCESS COMMAND
> /svn/immqt/db/__db.001
>                      root      16329 ....m  apache2
>                      root      16379 ....m  apache2
>                      root      16386 ....m  apache2
>                      root      16388 ....m  apache2
>                      root      16389 ....m  apache2
>                      root      16394 ....m  apache2
>                      root      16396 ....m  apache2
>                      root      16407 ....m  apache2
>                      ...
> 
> Regards,
> -------------------------------
> YamaKen  yamaken at bp.iij4u.or.jp

-------------------------------
YamaKen  yamaken at bp.iij4u.or.jp