You need to check the systemd journal for messages from onedrive.service. I had to run omv-onedrive --sync --resync to get it partly running. omv-onedrive is a wrapper command to use the correct configuration file and responsible for stopping and restarting the systemd service before executing the specified command line action; so do NOT use the onedrive command.
I think the new onedrive package is bugged. I got really strange journal messages like
Oct 27 18:47:12 omv7box (sleep)[14686]: onedrive.service: ProtectHostname=yes is configured, but UTS namespace setup is prohibited (container manager?), ignoring namespace setup.The strange thing is there is no ProtectHostname=yes setting in the onedrive systemd unit service file.
# systemctl cat onedrive.service
# /lib/systemd/system/onedrive.service
[Unit]
Description=OneDrive Free Client
After=network-online.target
Wants=network-online.target
[Service]
User=onedrive
Group=users
ExecStart=/usr/bin/onedrive --confdir /var/cache/onedrive --monitor
Restart=on-failure
RestartPreventExitStatus=3
RestartSec=3
[Install]
WantedBy=default.target
# /etc/systemd/system/onedrive.service.d/openmediavault.conf
[Unit]
RequiresMountsFor="/srv/dev-disk-by-uuid-e836df4b-58a3-41e4-88e6-ed6f4eaca171/"
[Service]
User=onedriveIt also seems to crash while downloading files.
Oct 27 18:47:32 omv7box onedrive[12474]: Downloading: <redacted> ... 30% | ETA 00:00:05
Oct 27 18:47:32 omv7box systemd[744]: Stopped onedrive.service - OneDrive Client for Linux.
Oct 27 18:47:32 omv7box systemd[744]: Starting onedrive.service - OneDrive Client for Linux...
Oct 27 18:47:32 omv7box (sleep)[14791]: onedrive.service: ProtectHostname=yes is configured, but UTS namespace setup is prohibited (container manager?), ignoring namespace setup.
Oct 27 18:47:32 omv7box onedrive[12474]: Downloading: <redacted>
More strange, it tries to authenticate during startup.Oct 27 18:47:47 omv7box systemd[744]: Started onedrive.service - OneDrive Client for Linux.
Oct 27 18:47:47 omv7box onedrive[14846]: WARNING: Required environment variables required to enable GUI Notifications are not present
Oct 27 18:47:47 omv7box onedrive[14846]: WARNING: The required environment variables to enable GUI Notifications are not available; GUI notifications are disabled
Oct 27 18:47:47 omv7box onedrive[14846]: Using IPv4 and IPv6 (if configured) for all network operations
Oct 27 18:47:47 omv7box onedrive[14846]: Attempting to contact Microsoft OneDrive Login Service
Oct 27 18:47:47 omv7box onedrive[12474]: Downloading: <redacted> ... 15% | ETA 00:00:12
Oct 27 18:47:47 omv7box onedrive[14846]: Successfully reached Microsoft OneDrive Login Service
Oct 27 18:47:47 omv7box onedrive[14846]: Configuring Global Azure AD Endpoints
Oct 27 18:47:47 omv7box onedrive[14846]: Authorise this application by visiting:
Oct 27 18:47:47 omv7box onedrive[14846]: https://login.microsoftonline.com/common/<redacted>
Oct 27 18:47:47 omv7box onedrive[14846]: Enter the response uri from your browser: An empty or invalid response uri was entered
Oct 27 18:47:47 omv7box onedrive[14846]: The OneDrive API could not be initialised
Oct 27 18:47:48 omv7box onedrive[12474]: Downloading: <redacted> ... 20% | ETA 00:00:12
Oct 27 18:47:48 omv7box systemd[744]: onedrive.service: Main process exited, code=exited, status=1/FAILURE
Oct 27 18:47:48 omv7box systemd[744]: onedrive.service: Failed with result 'exit-code'.
Oct 27 18:47:48 omv7box onedrive[12474]: Downloading: <redacted>abraunegg Any ideas what is going wrong here?
QuoteThe strange thing is there is no ProtectHostname=yes setting in the onedrive systemd unit service file.
That is a systemd issue .. nothing to do with the application. Take this up with the systemd developers
QuoteAny ideas what is going wrong here?
What version of 'curl' is OMV providing? Please read:
You have a couple of options here:
1. Provide to OMV users a more up-to-date version of 'curl'
2. Implement by 'default' the 'curl' downgrade options
Additionally, v2.5.3 will also implement some of these items, but also print warning messages when bad curl versions are being used by the platform.
Please also note - I did ask you to test v.2.5.x during the development phase to help iron out any issues with your OMV platform.
Also - from your systemd service file extract, it does not *match* what is from the source:
Your 'RestartPreventExitStatus=3` is incorrect.
This should read 'RestartPreventExitStatus=126' so that when a resync is required, the system does not keep restarting the systemd service.
Your logs also seem to indicate you have *multiple* onedrive processes running - one via the default systemd service and potentially one running manually.
Please double check / triple check all of your configuration(s) to ensure you *only* have one client running per application configuration.
The default Debian | Ubuntu packages *always* seem to install a default systemd service which can cause this sort of issue. Please read: https://github.com/abraunegg/o…a-or-distribution-package
Thanks for the response. I can not provide a newer curl package than Debian ships via their package repo for Debian 12, so i have to configure the downgrade options.
I've done the following changes. Due to how the plugin is running the service, i had to use onedrive@root.service and override some values because the configuration is stored at /var/cache/onedrive. Nevertheless, the service does not start even if i authenticate the app. The refresh_token is in /var/cache/onedrive.
# ls -alh /var/cache/onedrive/
total 1.6M
drwxr-xr-x 2 onedrive root 4.0K Oct 27 21:12 .
drwxr-xr-x 16 root root 4.0K Oct 25 18:36 ..
-rw------- 1 onedrive users 772 Oct 27 20:00 .config.backup
-rw------- 1 onedrive users 28 Oct 27 20:00 .config.hash
-rw-r--r-- 1 onedrive root 775 Oct 27 20:48 config
-rw-r--r-- 1 onedrive users 1.6M Oct 27 21:12 items.sqlite3
-rw-r----- 1 onedrive users 360 Oct 27 21:12 refresh_tokenOct 27 21:38:38 omv7box systemd[1]: Started onedrive@root.service - OneDrive Client for Linux running for root.
Oct 27 21:38:38 omv7box onedrive[18487]: Using 'user' configuration path for application config and state data: /var/log/onedrive/
Oct 27 21:38:38 omv7box onedrive[18487]: WARNING: Required environment variables required to enable GUI Notifications are not present
Oct 27 21:38:38 omv7box onedrive[18487]: WARNING: The required environment variables to enable GUI Notifications are not available; GUI notifications are disabled
Oct 27 21:38:38 omv7box onedrive[18487]: Using IPv4 and IPv6 (if configured) for all network operations
Oct 27 21:38:38 omv7box onedrive[18487]: Attempting to contact Microsoft OneDrive Login Service
Oct 27 21:38:38 omv7box onedrive[18487]: Successfully reached Microsoft OneDrive Login Service
Oct 27 21:38:38 omv7box onedrive[18487]: Checking Application Version ...
Oct 27 21:38:38 omv7box onedrive[18487]: Attempting to initialise the OneDrive API ...
Oct 27 21:38:38 omv7box onedrive[18487]: Configuring Global Azure AD Endpoints
Oct 27 21:38:38 omv7box onedrive[18487]: Authorise this application by visiting:
Oct 27 21:38:38 omv7box onedrive[18487]: https://login.microsoftonline.com/common/<redacted>>
Oct 27 21:38:38 omv7box onedrive[18487]: Enter the response uri from your browser: An empty or invalid response uri was entered
Oct 27 21:38:38 omv7box onedrive[18487]: The OneDrive API could not be initialised
Oct 27 21:38:39 omv7box systemd[1]: onedrive@root.service: Main process exited, code=exited, status=1/FAILURE
Oct 27 21:38:39 omv7box systemd[1]: onedrive@root.service: Failed with result 'exit-code'.Do you have an idea or hint how to get it working?
QuoteThanks for the response. I can not provide a newer curl package than Debian ships via their package repo for Debian 12, so i have to configure the downgrade options.
This is not accurate or correct. Debian 12 ships newer curl version (8.10.1) via Debian 12 Backports. Make sure you install:
from Debian 12 Backports and any other associated packages that these 2 pull in.
Curl 7.88.x is horribly broken as is 7.81 that Ubuntu uses.
QuoteDo you have an idea or hint how to get it working?
CodeUsing IPv4 and IPv6 (if configured) for all network operations
Based on your change you are not using those changes .. the application is still using IPv4 and IPv6 and defaulting to HTTP/2 operations.
So .. you need to rethink your change and how you are integrating the client to your platform to ensure that the client is reading the configuration file as specified.
Your 'OMV' configuration is not being read in / used, thus defaults are being used leading to all these issues.
To help you work out what is going on add to whatever method you are using to start the client
--display-running-configWhen using this option, the client will display all running configuration at startup to help you diagnose what is going on.
You can also use:
--display-configwhen just running the client manually, for example:
onedrive --display-config
This is not accurate or correct. Debian 12 ships newer curl version (8.10.1) via Debian 12 Backports. Make sure you install:
- curl
- libcurl4
from Debian 12 Backports and any other associated packages that these 2 pull in.
Curl 7.88.x is horribly broken as is 7.81 that Ubuntu uses.
OMV does not use and support backports because this breaks binary compatibility in some cases.
OMV is fixed to the stable repo only; thus it is guaranteed that the OMV code works.
OMV does not use and support backports because this breaks binary compatibility in some cases.
OMV is fixed to the stable repo only; thus it is guaranteed that the OMV code works.
Well you know what the fix is .. it is your platform and your choice in that manner. For your users there are only these 3 options to fix download:
This is the only way forward due to 'curl' bugs due to the version of 'curl' that Debian 12 ships with. Whilst the 'onedrive' client works around some of these bugs, the only true fix is to use a newer curl version.
Now .. the question always then is asked, why was this not seen with the v2.4.x client series?
Simple - for each operation a new 'curl' instance was created. This was time intensive, slow, inefficient amongst other items. It also did not allow then streamlining of operations to allow multi-threading to occur, which is why v2.5.x was a 20 month 100% re-write. Because of how curl was being used, it 100% masked the problematic curl versions that exist on certain platforms like Debian and Ubuntu.
Service cannot be started, not initialised (expected), systemd keeps restarting the service until the client is authenticated.
Not as per OneDrive GitHub Repository for the systemd service ... however this is an OMV platform item on how to handle.
forum.openmediavault.org/wsc/index.php?attachment/37930/
Issues with this file:
Add --display-running-config to see what the application is doing in a default state
Client is restarted by OMV and starts interacting with Microsoft OneDrive
Add --display-running-config to assist what configuration is actually being used and where are application files being accessed from
This helped me to identify the problem. Thx
Update systemd service file for correct exit not to restart code (126) when a --resync is required. The application should stop constantly restarting when exiting with a 126 value
The problem here is a strange problem of the Debian package from SUSE build service. If the old package is replaced bythe 2.5.2 one, it seems the old onedrive.service is not deleted and survives the package upgrade. Because of that i had a mixture of old and new systemd unit files. Using the onedrive@.service file will result in the expected behaviour.
Remove all config options that have been added, that are equal to their application 'default'. It is pointless having these set.
If the config file is manually generated then i am with you, but OMV is using a configuration management and orchestration tool to deploy the configuration. I'm too lazy to check if the config option matches the default or not. Second, if i'm doing a check, then i have to monitor the defaults per every update because they might change.
A new plugin package has been released.
A new plugin package has been released.
When was it released?
When was it released?
Appreciate it. I really like OMV because it is lightweight and easy to get up and running. However, this little issue is a thorn in my side. I'm not a Linux user so any help from people who know this stuff is a blessing. I just know enough to be dangerous. 😂
Don’t have an account yet? Register yourself now and be a part of our community!
