[csw-users] Webdav trouble
Nicolai Schwindt
schwindt at dfki.uni-kl.de
Tue Sep 1 20:18:08 CEST 2009
Last week I updated on of our production webserver to current.
.. and found I missed some tests before doing that.
The effect was all webdav enabled sources including svn stopped working
( one could still read, but not 'write').
The problem could be narrowed down to the DAVLockDB. So I hoped simply
downgrading dbd44 would fix this. In the end I had to downgrade these to get
back to normal :
software localrev remoterev
ap2_prefork 2.2.11,REV=2009.03.29 2.2.13,REV=2009.08.22
ap2_subversion 1.6.2,REV=2009.05.17 1.6.2,REV=2009.06.13
apache2 2.2.11,REV=2009.03.29 2.2.13,REV=2009.08.22
apache2c 2.2.11,REV=2009.03.29 2.2.13,REV=2009.08.22
apache2rt 2.2.11,REV=2009.03.29 2.2.13,REV=2009.08.22
berkeleydb44 4.4.20,REV=2009.05.26 4.4.20,REV=2009.07.28
subversion 1.6.2,REV=2009.05.17 1.6.2,REV=2009.06.13
I could reprocude the effect on another machine with simmilar setup
( SunOS isg-1516 5.10 Generic_141415-09 i86pc i386 i86pc )
Fiddling around with the packages ( trying to update any combination of it )
led always to the
effect of a failure when trying to PUT data. The affected process will crash.
Logs will look like this :
DB->get_multiple: method not permitted before handle's open method
[Tue Sep 01 18:36:05 2009] [notice] child pid 21239 exit signal Segmentation
fault (11)
truss tells :
1975: stat64("/opt/csw/apache2/lib/apr_dbm_db-1.so", 0x080469F0) Err#2 ENOENT
1975: stat64("/opt/csw/apache2/lib/apr-util-1/apr_dbm_db-1.so", 0x080469F0)
Err#2 ENOENT
1975: stat64("/opt/csw/apache2/lib/apr-util-1/apr_dbm_db-1.so", 0x080469F0)
Err#2 ENOENT
1975: stat64("/export/serv-2300a/webdav/calendars/gf/Privat.ics",
0x080476B0) Err#2 ENOENT
1975: Incurred fault #6, FLTBOUNDS %pc = 0xFEF6C1E4
1975: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000050
1975: Received signal #11, SIGSEGV [caught]
1975: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000050
1975: lwp_sigmask(SIG_SETMASK, 0x00000400, 0x00000000) = 0xFFBFFEFF
[0x0000FFFF]
Switching to apache/svn from testing and dbd4 from current.
The error log holds:
[Tue Sep 01 19:14:51 2009] [error] [client 192.168.15.207] The locks could not
be queried for verification against a possible "If:" header. [500, #0]
[Tue Sep 01 19:14:51 2009] [error] [client 192.168.15.207] Could not open the
lock database. [500, #400]
[Tue Sep 01 19:14:51 2009] [error] [client 192.168.15.207] (11)Resource
temporarily unavailable: Could not open property database. [500, #1]
Right now I guess apache_rt could be the problem but I am not sure about that.
I'll try to dig deeper.
Has anyone similar effects ?
Nicolai
More information about the users
mailing list