Re: "Not supported" message while a file upload

Hi Jan,

On Wed, Jun 21, 2017 at 08:23:59PM +0000, Jan Schneider wrote:
>Zitat von Christian Schoepplein <[email protected]>:
>> I am using the latest horde and gollem packages and have configured a
>> samba backend for my users. The backend definition looks like this,
>> $servername is queried befor via a sql statement because the users are
>> located on different servers:
>> 
>>     $backends['smb'] = array(
>>       'disabled' => false,
>>       'name' => 'Home Verzeichnis auf Schulserver',
>>       'driver' => 'smb',
>>       'hordeauth' => true,
>>       'params' => array(
>>         'hostspec' => $servername,
>>         'port' => 139,
>>         'share' => 'homes',
>>         'smbclient' => '/usr/bin/smbclient',
>>         'permissions' => '750'
>>       ),
>>       'loginparams' => array(
>>           // Allow the user to change to Samba server.
>>           // 'hostspec' => '$servername',
>>           // Allow the user to change the Samba port.
>>           // 'port' => 'Port',
>>           // Allow the user to change the Samba share.
>>           // 'share' => 'Share',
>>       ),
>>       // 'root' => '',
>>       // 'home' => '',
>>       'createhome' => false,
>>       // 'filter' => '^regex$',
>>       'quota' => false,
>>       'attributes' => array(
>>         'type',
>>         'name',
>>         'edit',
>>         'download',
>>         'modified',
>>         'size'
>>       )
>>     );
>> 
>> When the users try to upload a file they get a message that just shows
>> "Not supported" and the file is not stored on the server. If the upload
>> is repeated immediately after the first try, the upload works and the
>> file shows up on the server.
>> 
>> So the upload seems to be working, but it has to be repeated because the
>> first try failes.
>> 
>> Has anyone a hint what the "not supported" message means and why the
>> upload is not working during the first try? How can I debug this
>> behaviour? I did not find something related in the webserver logs on the
>> horde server, on our reverse proxy or on the samba backend :-(.
>
>Try setting the log level to DEBUG so that you get a backtrace to that error.

Will try this when not that much users are working with the system, 
thanks.

As a workaround I switched to a ftp backend. That seems to work better, 
but I can see many lines like this in the horde log:

2017-06-22T07:44:56+00:00 WARN: HORDE [gollem] PHP ERROR: rewind(): 
stream does not support seeking [pid 30057 on line 1770 of 
"/usr/share/php/Horde/Mime/Part.php"]
2017-06-22T07:44:56+00:00 WARN: HORDE [gollem] PHP ERROR: fseek(): 
stream does not support seeking [pid 30057 on line 73 of 
"/var/www/horde/gollem/view.php"]

Is that something that can be ignored or what is causing this errors and 
what can / should I do to prevent them?

Ciao and thanks,

  Schoepp

-- 
Christian Schoepplein

Landeshauptstadt Muenchen
Referat fuer Bildung und Sport
Zentrum fuer Informationstechnologie im Bildungsbereich (ZIB)
- Netze und Servermanagement

Postanschrift:                          Bueroanschrift:

Landeshauptstadt Muenchen               Landeshauptstadt Muenchen
Referat fuer Bildung und Sport          Referat fuer Bildung und Sport
Postfach                                Bayerstr. 28 (Raum 5.326)

80313 Muenchen                          80335 Muenchen

T: +49 (0)89 233-87623
E: c.schoepplein (at) musin.de
I: http://www.zib.musin.de

Elektronische Kommunikation mit der Landeshauptstadt Muenchen, siehe: 
http://www.muenchen.de/ekomm

Bitte denken Sie an die Umwelt, bevor Sie diese E-Mail ausdrucken. Pro 
Blatt sparen Sie durchschnittlich 15g Holz, 260ml Wasser, 0,05kWh Strom 
und 5g CO2.


-- 
gollem mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]