Nuxeo Drive FAQ

This page non exhaustively lists frequently asked questions about Nuxeo Drive

How to Configure the Synchronization Delay

Since the version 1.3.1216 of Nuxeo Drive client, the synchronization delay is 30 seconds (5 seconds in the previous releases). There are three ways to change this value:

1. For test purpose, run Nuxeo Drive in console mode with the --delay parameter:

ndrive --delay=120

1. Add a config.ini file in the folder C:\Users\<username>\.nuxeo-drive with the following lines:

[DEFAULT]
env=longDelay

[longDelay]
delay=120

This example sets the delay to 120 seconds by activating the longDelay setting environment.

1. Finally, if you want to change the delay for all the Nuxeo Drive clients, you can update the delay setting of the Nuxeo Drive global configuration.

How to Change the Log Verbosity

1. The simplest way is through the Advanced tab of the Settings panel.

2. This can also done as for the previous paragraph by adding the following lines in the config.ini file:

   • Increase log verbosity:

     log-level-file=TRACE
     

   • Decrease log verbosity:

     log-level-file=ERROR
     

3. Finally, if you want to change the log verbosity for all the Nuxeo Drive clients, you can update the log_level_file setting of the Nuxeo Drive global configuration.

How to Change the Synchronization Folder

The configuration of the synchronization folder needs to be done at the first setup of Drive.

In the Settings screen, you can switch to another folder by clicking on the ... button, as you can see on this picture.

How to Make Nuxeo Drive Work with a Nuxeo Cluster

Nuxeo LTS 2015 and higher

You only need to make sure that:

• Redis is enabled.
• The $DATA_DIR/transientstores/default directory is shared by all the Nuxeo instances, see the related documentation for details.

Nuxeo 7.4 and lower

You can:

• Configure Apache with mod_proxy_balancer to use load balancing with stickyness.

  Apache-side sticky session

  Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED
  <Proxy balancer://nuxeocluster>
      BalancerMember http://nuxeo1:8080 route=1
      BalancerMember http://nuxeo2:8080 route=2
  ProxySet stickysession=ROUTEID
  </Proxy>
  ProxyPass        "/" "balancer://nuxeocluster/"
  ProxyPassReverse "/" "balancer://nuxeocluster/"
  ProxyPreserveHost On
  

  Also see https://wiki.apache.org/httpd/LoadBalanceWithoutStickyCookie.

• Use AWS Elastic Load Balancing with sticky sessions.

How to Report Bugs or Problems about Nuxeo Drive Usage

If you want to report any issue regarding Nuxeo Drive, you need to provide these informations:

• Drive client version, for example 2.0.0911: this information can be found in the Settings > About menu when doing a right-click on Nuxeo Drive icon in the systray
• Drive package version, for example 1.4.4: this information can be found in Admin > Update Center > Local packages (administrator rights are needed to access this section)
• Nuxeo Platform version, for example 6.0, and the level of hotfixes installed
• Bug report generated by Nuxeo Drive, see Settings > Advanced > Click to generate a bug report.
• Drive client logs, located in C:\Users\<username>\.nuxeo-drive\logs\nxdrive.log
• Nuxeo Platform logs, located in $NUXEO/log/server.log by default

Limitations

Currently Nuxeo Drive has some limitations:

• Synchronizing very big files may be an issue if your network connection is slow or unstable. This will be improved by uploading files by chunks and allowing to resume uploads, see NXDRIVE-457.
• The target use case is not to synchronize a huge tree on a lot of desktops: Nuxeo Drive is not optimized to replicate the Document Repository on each desktop.
• Complex synchronization cases where you delete files that are being synchronized.
• Drive will generates errors and will ignore files that are duplicates on the server. Thus, it is not recommended to have an extensive usage of Nuxeo Drive with plateform use cases implying file duplicates.

---