2,187
edits
Difference between revisions of "Troubleshooting (Z-Push)"
Jump to navigation
Jump to search
m
Spelling corrections etc
(Initial creation) |
m (Spelling corrections etc) |
||
| Line 28: | Line 28: | ||
#* If you get a blank page and nothing else, the webserver (eg Apache) is failing to deliver the page. This is most likely due to a PHP error and you'll need to look at the webserver logs. | #* If you get a blank page and nothing else, the webserver (eg Apache) is failing to deliver the page. This is most likely due to a PHP error and you'll need to look at the webserver logs. | ||
#* You should be prompted for a username and password (for an account on your Zimbra server), in which case your webserver is working correctly | #* You should be prompted for a username and password (for an account on your Zimbra server), in which case your webserver is working correctly | ||
# Enter a valid Zimbra | # Enter a valid Zimbra account user/pass | ||
#* You should get a "GET not supported" page | #* You should get a "GET not supported" page | ||
#* If not, then Z-Push is unable to | #* If not, then Z-Push is unable to successfully authenticate the supplied user/pass, investigate the Zimbra audit logs | ||
Assuming the above works, then the basic configuration and interconnectivity of the components (excluding mobile devices) is working. | Assuming the above works, then the basic configuration and interconnectivity of the components (excluding mobile devices) is working. | ||
Tailing the [[#Z-Push|Z-Push log]] (EG <code>tail -f /var/www/z-push/debug.txt</code>) whilst forcing a device to sync can be worth a try, in case there are some | Tailing the [[#Z-Push|Z-Push log]] (EG <code>tail -f /var/www/z-push/debug.txt</code>) whilst forcing a device to sync can be worth a try, in case there are some obvious errors to fix. If you're not seeing any activity in the Z-Push log for the device, that suggests that the device is either failing to initiate a sync, or is unable to reach the ActiveSync URL. | ||
== Logging == | == Logging == | ||
If possible, limit the amount of syncing that's taking place when investigating a problem in the logs. Stop any devices that you can from syncing, and especially on a specific device you're interested in, stop all syncing, and then manually force a sync for a particular data type (calendar, contacts, etc). You're ability to do this will be governed by your users, and types of devices that are syncing. | |||
=== Z-Push === | === Z-Push === | ||
By default Z-Push will log to <code>debug.txt</code>, though this will only work if the webserver has write access. Similarly the logging cannot be turned off, so to prevent a large logfile remove write access to the file. | By default Z-Push will log to <code>debug.txt</code>, though this will only work if the webserver has write access. Similarly the logging cannot be turned off, so to prevent a large logfile remove write access to the file. | ||