Ok, I really installed ownCloud on my server just for that (and on the way, configured LDAP/SMB shares). I bought the open source app just for this (because thanks to Apple, there's not even a way to build it yourself from sources and transfer to the device). I do see now how it 'works' now. I can open the kdbx file WITHIN the owncloud app. Then good news, because the ownCloud iOS App enables you to connect iOS devices to a private ownCloud server running in your data center. OwnCloud is open source file sync and share software for everyone from individuals operating the free ownCloud server, to large enterprises and service providers operating under ownCloud Enterprise subscriptions.
The following two general issues can result in failed synchronization:
- The server setup is incorrect.
- The client contains a bug.
When reporting bugs, it is helpful if you first determine what part of thesystem is causing the issue.
Identifying Basic Functionality Problems¶
Performing a general ownCloud Server test: | |
---|---|
The first step in troubleshooting synchronization issues is to verify thatyou can log on to the ownCloud web application. To verify connectivity to theownCloud server try logging in via your Web browser. If you are not prompted for your username and password, or if a red warningbox appears on the page, your server setup requires modification. Please verifythat your server installation is working correctly. | |
Ensure the WebDAV API is working: | |
If all desktop clients fail to connect to the ownCloud Server, but accessusing the Web interface functions properly, the problem is often amisconfiguration of the WebDAV API. The ownCloud Client uses the built-in WebDAV access of the server content.Verify that you can log on to ownClouds WebDAV server. To verify connectivitywith the ownCloud WebDAV server:
For example, if your ownCloud instance is installed at http://yourserver.com/owncloud , your WebDAV server address ishttp://yourserver.com/owncloud/remote.php/webdav .If you are prompted for your username and password but, after providing thecorrect credentials, authentication fails, please ensure that yourauthentication backend is configured properly. | |
Use a WebDAV command line tool to test: | |
A more sophisticated test method for troubleshooting synchronization issuesis to use a WebDAV command line client and log into the ownCloud WebDAV server.One such command line client – called cadaver – is available for Linuxdistributions. You can use this application to further verify that the WebDAVserver is running properly using PROPFIND calls.As an example, after installing the cadaver app, you can issue thepropget command to obtain various properties pertaining to the currentdirectory and also verify WebDAV server connection. |
Isolating other issues¶
Other issues can affect synchronization of your ownCloud files:
- If you find that the results of the synchronizations are unreliable, pleaseensure that the folder to which you are synchronizing is not shared withother synchronization applications.
- Synchronizing the same directory with ownCloud and other synchronizationsoftware such as Unison, rsync, Microsoft Windows Offline Folders, or othercloud services such as DropBox or Microsoft SkyDrive is not supported andshould not be attempted. In the worst case, it is possible that synchronizingfolders or files using ownCloud and other synchronization software orservices can result in data loss.
- If you find that only specific files are not synrchronized, thesynchronization protocol might be having an effect. Some files areautomatically ignored because they are system files, other files might beignored because their filename contains characters that are not supported oncertain file systems. For more information about ignored files, see_ignored-files-label.
- If you are operating your own server, and use the local storage backend (thedefault), make sure that ownCloud has exclusive access to the directory.NoteThe data directory on the server is exclusive to ownCloud and must not be modified manually.
- If you are using a different file backend on the server, you can try to exclude a bug in thebackend by reverting to the built-in backend.
- If you are experiencing slow upload/download speed or similar performance issuesbe aware that those could be caused by on-access virus scanning solutions, eitheron the server (like the files_antivirus app) or the client.
Log Files¶
Effectively debugging software requires as much relative information as can beobtained. To assist the ownCloud support personnel, please try to provide asmany relevant logs as possible. How to change thumbnail on mac app. Log output can help with tracking downproblems and, if you report a bug, log output can help to resolve an issue morequickly.
Obtaining the Client Log File¶
To obtain the client log file: Best organization mac apps.
- Open the ownCloud Desktop Client.
- Press F12 on your keyboard.
- Click the ‘Save’ button.
Ipad app on mac. The Save Log File window opens.
- Migrate to a location on your system where you want to save your log file.
- Name the log file and click the ‘Save’ button.
Alternatively, you can launch the ownCloud Log Output window using the
--logwindow
command. After issuing this command, the Log Output windowopens to show the current log. You can then follow the same proceduresmentioned above to save the log to a file.Note
You can also open a log window for an already running session, byrestarting the client using the following command:
- Windows:
C:ProgramFiles(x86)ownCloudowncloud.exe--logwindow
- Mac OS X:
/Applications/owncloud.app/Contents/MacOS/owncloud--logwindow
- Linux:
owncloud--logwindow
Saving Files Directly¶
The ownCloud client enables you to save log files directly to a predefined fileor directory. This is a useful option for troubleshooting sporadic issues asit enables you to log large amounts of data and bypasses the limited buffersettings associated with the log window.
To save log files to a file or a directory:
- To save to a file, start the client using the
--logfile<file>
command,where<file>
is the filename to which you want to save the file. - To save to a directory, start the client using the
--logdir<dir>
command, where<dir>
is an existing directory.
When using the
--logdir
command, each sync run creates a new file. To limitthe amount of data that accumulates over time, you can specify the--logexpire<hours>
command. When combined with the --logdir
command,the client automatically erases saved log data in the directory that is olderthan the specified number of hours.As an example, to define a test where you keep log data for two days, you canissue the following command:
`owncloud--logdir/tmp/owncloud_logs--logexpire48`
ownCloud server Log File¶
The ownCloud server also maintains an ownCloud specific log file. This log filemust be enabled through the ownCloud Administration page. On that page, you canadjust the log level. We recommend that when setting the log file level thatyou set it to a verbose level like
Debug
or Info
.You can view the server log file using the web interface or you can open itdirectly from the file system in the ownCloud server data directory.
Todo
Need more information on this. How is the log file accessed?Need to explore procedural steps in access and in saving this file .. similarto how the log file is managed for the client. Perhaps it is detailed in theAdmin Guide and a link should be provided from here. I will look into thatwhen I begin heavily editing the Admin Guide.
Webserver Log Files¶
It can be helpful to view your webservers error log file to isolate anyownCloud-related problems. For Apache on Linux, the error logs are typicallylocated in the
/var/log/apache2
directory. Some helpful files include thefollowing:error_log
– Maintains errors associated with PHP code.access_log
– Typically records all requests handled by the server; veryuseful as a debugging tool because the log line contains information specificto each request and its result.
You can find more information about Apache logging at
http://httpd.apache.org/docs/current/logs.html
.Core Dumps¶
On Mac OS X and Linux systems, and in the unlikely event the client softwarecrashes, the client is able to write a core dump file. Obtaining a core dumpfile can assist ownCloud Customer Support tremendously in the debuggingprocess.
To enable the writing of core dump files, you must define the
OWNCLOUD_CORE_DUMP
environment variable on the system.For example:
Best photo booth app mac.
`OWNCLOUD_CORE_DUMP=1owncloud`
This command starts the client with core dumping enabled and saves the files inthe current working directory.
Note
Mac App Store Cannot Open
Core dump files can be fairly large. Before enabling core dumps onyour system, ensure that you have enough disk space to accommodate these files.Also, due to their size, we strongly recommend that you properly compress anycore dump files prior to sending them to ownCloud Customer Support.