0-Byte Files

[Phhere]

Hello,
sometimes we get 0-byte files on our server. This seems to be known to sabre-dav but is your put-method aware of this? There is some explanation available at http://sabre.io/dav/0bytes/

Server-Info:
Red Hat Enterprise Linux 7.2
Apache/2.4.6
PHP 7.0.9

Here is a part of the log:

2016-08-17 20:47:44: trace: SambaDAV\Directory::getQuotaInfo: '//server/daten/__Projekte_ZIM'
2016-08-17 20:47:44: info: proc_open(/usr/bin/smbclient --debuglevel=0 --authentication-file=/proc/self/fd/3 '//server/daten', ...)
2016-08-17 20:47:44: trace: SambaDAV\Directory::getQuotaInfo: '//server/daten/__Info_ZIM'
2016-08-17 20:47:44: trace: SambaDAV\Directory::getQuotaInfo: '//server/daten/__Info_ZIM'
2016-08-17 20:47:44: trace: SambaDAV\Directory::getQuotaInfo: '//server/daten/HPC'
2016-08-17 20:47:44: trace: SambaDAV\Directory::getQuotaInfo: '//server/daten/HPC'
2016-08-17 20:47:44: trace: SambaDAV\Directory::getQuotaInfo: '//server/daten/IT-Sicherheit'
2016-08-17 20:47:44: trace: SambaDAV\Directory::getQuotaInfo: '//server/daten/IT-Sicherheit'
2016-08-17 20:47:44: trace: SambaDAV\SMBClient\Process::writeAuthFile
2016-08-17 20:47:44: trace: SambaDAV\SMBClient\Process::writeCommand
2016-08-17 20:47:45: trace: SambaDAV\Directory::createFile: '//server/daten/test.file'
2016-08-17 20:47:45: trace: SambaDAV\SMB::put: '//server/daten/test.file'
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::open: ''//server/daten'', 'cd "/"
put /proc/self/fd/4 "test.file"'
2016-08-17 20:47:45: info: proc_open(/usr/bin/smbclient --debuglevel=0 --authentication-file=/proc/self/fd/3 '//server/daten', ...)
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::writeAuthFile
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::writeCommand
2016-08-17 20:47:45: warn: EXCEPTION: 'ad\user' not authenticated for '//server/daten'
2016-08-17 20:47:45: debug: skipping LDAP authentication
2016-08-17 20:47:45: info: login accepted for 'ad\user'
2016-08-17 20:47:45: trace: SambaDAV\Directory::getChild: '//' 'zim'
2016-08-17 20:47:45: trace: SambaDAV\SMB::getShares: '//server.xxxxx'
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::open: '--grepable --list '//server.xxxxx'', ''
2016-08-17 20:47:45: info: proc_open(/usr/bin/smbclient --debuglevel=0 --authentication-file=/proc/self/fd/3 --grepable --list '//server.xxxxx', ...)
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::writeAuthFile
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::writeCommand
2016-08-17 20:47:45: trace: SambaDAV\Directory::getChild: '//server' 'daten'
2016-08-17 20:47:45: trace: SambaDAV\SMB::ls: '//server/daten'
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::open: ''//server/daten'', 'cd "/"
ls'
2016-08-17 20:47:45: info: proc_open(/usr/bin/smbclient --debuglevel=0 --authentication-file=/proc/self/fd/3 '//server/daten', ...)
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::writeAuthFile
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::writeCommand
2016-08-17 20:47:45: trace: SambaDAV\Directory::createFile: '//server/daten/test.file'
2016-08-17 20:47:45: trace: SambaDAV\SMB::put: '//server/daten/test.file'
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::open: ''//server/daten'', 'cd "/"
put /proc/self/fd/4 "test.file"'
2016-08-17 20:47:45: info: proc_open(/usr/bin/smbclient --debuglevel=0 --authentication-file=/proc/self/fd/3 '//server/daten', ...)
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::writeAuthFile
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::writeCommand
2016-08-17 20:47:45: warn: EXCEPTION: 'ad\user' not authenticated for '//server/daten'
2016-08-17 20:47:45: debug: skipping LDAP authentication
2016-08-17 20:47:45: info: login accepted for 'ad\user'
2016-08-17 20:47:45: trace: SambaDAV\Directory::getChild: '//' 'zim'
2016-08-17 20:47:45: trace: SambaDAV\SMB::getShares: '//server.xxxxx'
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::open: '--grepable --list '//server.xxxxx'', ''
2016-08-17 20:47:45: info: proc_open(/usr/bin/smbclient --debuglevel=0 --authentication-file=/proc/self/fd/3 --grepable --list '//server.xxxxx', ...)
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::writeAuthFile
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::writeCommand
2016-08-17 20:47:45: trace: SambaDAV\Directory::getChild: '//server' 'daten'
2016-08-17 20:47:45: trace: SambaDAV\SMB::ls: '//server/daten'
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::open: ''//server/daten'', 'cd "/"
ls'
2016-08-17 20:47:45: info: proc_open(/usr/bin/smbclient --debuglevel=0 --authentication-file=/proc/self/fd/3 '//server/daten', ...)
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::writeAuthFile
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::writeCommand
2016-08-17 20:47:45: trace: SambaDAV\Directory::createFile: '//server/daten/test.file'
2016-08-17 20:47:45: trace: SambaDAV\SMB::put: '//server/daten/test.file'
2016-08-17 20:47:45: trace: SambaDAV\SMBClient\Process::open: ''//server/daten'', 'cd "/"
put /proc/self/fd/4 "test.file"'

[marcovanbeek]

Hi,

I just resolved a similar problem by making sure that Apache could write to the data directory where it keeps the local file database.
Look for an error in the Apache error log file where it talks about locks.dat if it is the same thing.