[Pkg-owncloud-commits] [owncloud-doc] 30/71: Backport #929 and #1014 to stable7
David Prévot
taffit at moszumanska.debian.org
Sun May 31 01:58:38 UTC 2015
This is an automated email from the git hooks/post-receive script.
taffit pushed a commit to branch master
in repository owncloud-doc.
commit b4d6e834c7d2c0b1cba615497f7b02130ea11f1c
Author: RealRancor <Fisch.666 at gmx.de>
Date: Sat Apr 4 14:53:51 2015 +0200
Backport #929 and #1014 to stable7
---
admin_manual/issues/index.rst | 102 ++++++++++++++++++++++++++++++++----
user_manual/pim/troubleshooting.rst | 76 +--------------------------
2 files changed, 93 insertions(+), 85 deletions(-)
diff --git a/admin_manual/issues/index.rst b/admin_manual/issues/index.rst
index ad70792..e9bb837 100644
--- a/admin_manual/issues/index.rst
+++ b/admin_manual/issues/index.rst
@@ -35,14 +35,55 @@ If you can't find a solution, please use our `bugtracker`_.
.. _Enterprise Edition: https://owncloud.com/lp/community-or-enterprise/
.. _bugtracker: http://doc.owncloud.org/server/7.0/developer_manual/bugtracker/index.html
+General Troubleshooting
+-----------------------
+
+Debugging the issue
+~~~~~~~~~~~~~~~~~~~
+
+In a standard ownCloud installation the log level is set to "Normal". to find any issues
+you need to raise the log level to "All" from the Admin page. Please see :doc:`../configuration/logging_configuration`
+for more informations on this log levels.
+
+Some logging - for example JavaScript console logging - needs manually editing the
+configuration file.
+Edit :file:`config/config.php` and add ``define('DEBUG', true);``::
+
+ <?php
+ define('DEBUG',true);
+ $CONFIG = array (
+ ... configuration goes here ...
+ );
+
+For JavaScript issues you will also need to view the javascript console. All major browsers
+have decent developer tools for viewing the console, and you usually access them by
+pressing F-12. For Firefox it is recommended to install the `Firebug extension <https://getfirebug.com/>`_.
+
+.. note:: The logfile of ownCloud is located in the datadirectory ``/var/www/owncloud/data/owncloud.log``.
+
+Debugging Sync-Issues
+~~~~~~~~~~~~~~~~~~~~~
+
+.. note:: The data directory on the server is exclusive to ownCloud and must not be modified manually.
+
+Disregarding this can lead to unwanted behaviours like:
+
+* Problems with sync clients
+* Undetected changes due to caching in the database
+
+If you need to directly upload files from the same server please use a WebDAV command
+line client like `cadaver` to upload files to the WebDAV interface at:
+
+ https://example.org/owncloud/remote.php/webdav
+
Troubleshooting Webserver and PHP problems
------------------------------------------
Logfiles
~~~~~~~~
-When having issues the first step is to check the logfiles provided by PHP and
-the Webserver.
+When having issues the first step is to check the logfiles provided by PHP, the Webserver
+and ownCloud itself.
.. note:: In the following the paths to the logfiles of a default Debian installation
running Apache2 with mod_php is assumed. On other webservers, linux distros or
@@ -112,17 +153,56 @@ helpful. See:
<http://sabre.io/dav/clients/finder/>`_
(Describes problems with Finder on various webservers)
-General Troubleshooting
------------------------
+Troubleshooting Contacts & Calendar
+-----------------------------------
-.. note:: The data directory on the server is exclusive to ownCloud and must not be modified manually.
+Service discovery
+~~~~~~~~~~~~~~~~~
-Disregarding this can lead to unwanted behaviours like:
+Some clients - especially iOS - have problems finding the proper sync URL, even when explicitly
+configured to use it.
-* Problems with sync clients
-* Undetected changes due to caching in the database
+There are several techniques to remedy this, which are described extensively at the
+`Sabre DAV website <http://sabre.io/dav/service-discovery/>`_.
-If you need to directly upload files from the same server please use a WebDAV command
-line client like `cadaver` to upload files to the WebDAV interface at:
+Apple iOS
+~~~~~~~~~
- https://example.org/owncloud/remote.php/webdav
+Below is what have proven to work with iOS including iOS 7.
+
+If your ownCloud instance is installed in a subfolder under the web server's document root and
+the client has difficulties finding the Cal- or CardDAV end-points, configure your web server to
+redirect from a "well-know" URL to the one used by ownCloud.
+When using the Apache web server this is easily achieved using a :file:`.htaccess` file in the document
+root of your site.
+
+Say your instance is located in the ``owncloud`` folder, so the URL to it is ``ADDRESS/owncloud``,
+create or edit the :file:`.htaccess` file and add the following lines::
+
+ Redirect 301 /.well-known/carddav /owncloud/remote.php/carddav
+ Redirect 301 /.well-known/caldav /owncloud/remote.php/caldav
+
+If you use lighttpd as web server, the setting looks something like::
+
+ url.redirect = (
+ "^/.well-known/carddav" => "/owncloud/remote.php/carddav",
+ "^/.well-known/caldav" => "/owncloud/remote.php/caldav",
+ )
+
+Now change the URL in the client settings to just use ``ADDRESS`` instead of e.g. ``ADDRESS/remote.php/carddav/principals/username``.
+
+This problem is being discussed in the `forum <http://forum.owncloud.org/viewtopic.php?f=3&t=71&p=2211#p2197>`_.
+
+Unable to update Contacts or Events
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If you get an error like ``PATCH https://ADDRESS/some_url HTTP/1.0 501 Not Implemented`` it is
+likely caused by one of the following reasons:
+
+Outdated lighttpd web server
+ lighttpd in debian wheezy (1.4.31) doesn't support the PATCH HTTP verb.
+ Upgrade to lighttpd >= 1.4.33.
+
+Using Pound reverse-proxy/load balancer
+ As of writing this Pound doesn't support the HTTP/1.1 verb.
+ Pound is easily `patched <http://www.apsis.ch/pound/pound_list/archive/2013/2013-08/1377264673000>`_ to support HTTP/1.1.
diff --git a/user_manual/pim/troubleshooting.rst b/user_manual/pim/troubleshooting.rst
index 4f85be7..20802b9 100644
--- a/user_manual/pim/troubleshooting.rst
+++ b/user_manual/pim/troubleshooting.rst
@@ -1,65 +1,8 @@
Troubleshooting
===============
-Debugging the issue
--------------------
-
-In a standard ownCloud installation the log level is set to "Normal". to find any issues
-you need to raise the log level to "All" from the Admin page.
-Some logging - for example JavaScript console logging - needs manually editing the
-configuration file.
-Edit :file:`config/config.php` and add ``define('DEBUG', true);``::
-
- <?php
- define('DEBUG',true);
- $CONFIG = array (
- ... configuration goes here ...
- );
-
-For JavaScript issues you will also need to view the javascript console. All major browsers
-have decent developer tools for viewing the console, and you usually access them by
-pressing F-12. For Firefox it is recommended to install the `Firebug extension <https://getfirebug.com/>`_.
-
-Service discovery
------------------
-
-Some clients - especially iOS - have problems finding the proper sync URL, even when explicitly
-configured to use it.
-
-There are several techniques to remedy this, which are described extensively at the
-`Sabre DAV website <http://sabre.io/dav/service-discovery/>`_.
-
-Apple iOS
-`````````
-
-Below is what have proven to work with iOS including iOS 7.
-
-If your ownCloud instance is installed in a subfolder under the web server's document root and
-the client has difficulties finding the Cal- or CardDAV end-points, configure your web server to
-redirect from a "well-know" URL to the one used by ownCloud.
-When using the Apache web server this is easily achieved using a :file:`.htaccess` file in the document
-root of your site.
-
-Say your instance is located in the ``owncloud`` folder, so the URL to it is ``ADDRESS/owncloud``,
-create or edit the :file:`.htaccess` file and add the following lines::
-
- Redirect 301 /.well-known/carddav /owncloud/remote.php/carddav
- Redirect 301 /.well-known/caldav /owncloud/remote.php/caldav
-
-If you use lighttpd as web server, the setting looks something like::
-
- url.redirect = (
- "^/.well-known/carddav" => "/owncloud/remote.php/carddav",
- "^/.well-known/caldav" => "/owncloud/remote.php/caldav",
- )
-
-Now change the URL in the client settings to just use ``ADDRESS`` instead of e.g. ``ADDRESS/remote.php/carddav/principals/username``.
-
-This problem is being discussed in the `forum <http://forum.owncloud.org/viewtopic.php?f=3&t=71&p=2211#p2197>`_.
-
-
BlackBerry OS 10.2
-``````````````````
+------------------
BlackBerry OS up to 10.2.2102 does not accept a URL with protocol ``https://`` in front of the server address.
It will always tell you, that it cannot login on your server. So instead of writing
@@ -68,19 +11,4 @@ It will always tell you, that it cannot login on your server. So instead of writ
in the server address field, you have to write
- address/remote.php/carddav/principals/username
-
-
-Unable to update Contacts or Events
------------------------------------
-
-If you get an error like ``PATCH https://ADDRESS/some_url HTTP/1.0 501 Not Implemented`` it is
-likely caused by one of the following reasons:
-
-Outdated lighttpd web server
- lighttpd in debian wheezy (1.4.31) doesn't support the PATCH HTTP verb.
- Upgrade to lighttpd >= 1.4.33.
-
-Using Pound reverse-proxy/load balancer
- As of writing this Pound doesn't support the HTTP/1.1 verb.
- Pound is easily `patched <http://www.apsis.ch/pound/pound_list/archive/2013/2013-08/1377264673000>`_ to support HTTP/1.1.
+ address/remote.php/carddav/principals/username
\ No newline at end of file
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-owncloud/owncloud-doc.git
More information about the Pkg-owncloud-commits
mailing list