Odrive frequently not running

[scott3]

This is an ongoing issue, so finally decided to post here.

Running odrive on a Mac that’s currently on MacOS Ventura 13.1. The issue is, I often find odrive is no longer running. Usually when I need a file on another computer running odrive or looking for something in my google drive account that hasn’t yet uploaded.

Odrive is listed in the “Open at login” list under Ventura Settings > Login Items. Not sure if it’s not launching on restart or it crashes and closes. Or if my finder’s crashing and odrive closes with it.

Thoughts?

[Tony]

Hi @scott3,
We can certainly investigate. We haven’t had any crash reports for a couple of years now, so there may be something else at play here.

Can you please do the following?

1. Send a diagnostic from the odrive tray menu:

How do I send a diagnostic?

When you send a diagnostic, the odrive desktop client will provide a report to odrive that contains lower-level information that may be necessary to troubleshoot a particular issue. A local report is also generated that you can look at. You can find this report, named “current_odrive_status.txt” in the root of the default odrive folder. To send a diagnostic: On Windows: Open up the odrive tray menu, located in the Windows taskbar Click on “Send diagnostics”, located at the bottom of the me…

2. Type console into Spotlight to find and open the console. You will see “Crash Reports” listed in the left-hand column. If there are any listed for odrive, right-click on it and select “Reveal in Finder”, then upload it here so that we can take a look.

Just let me know when you are able to get to the items above.

[scott3]

Hi Tony.

Diag report sent. There are no odrive crash reports as of 2/27. Not sure how long odrive hadn’t been running, this time. FYI, I just did a restart and see odrive has launched. So werid that it vanishes. I have noticed I sometimes come back to my computer to find all apps closed, which indicates to me finder crashed and relaunched, which could mean all login item apps had closed to?

[Tony]

Hi @scott3,
Since you are not seeing any crash reports, it doesn’t seem like odrive is crashing.

@scott3

I sometimes come back to my computer to find all apps closed

Even if Finder crashes, odrive will continue running since it is running as a separate application and only has a small component that is used with Finder.

Since you are seeing all of your apps closed, that may indicate something else. Is it possible your computer is rebooting?

Try the following:

1. Open up a terminal window (type “terminal” in spotlight)
2. In the terminal window type “uptime” and hit return. This will tell us how long the computer has been “up”
3. In the terminal window type “last” and hit return. This will show all of the previous logins, shutdowns, and reboots.

[scott3]

Good tip. I ran it and see results (of course). I’ll keep an eye on this the next time everything is closed. Anything else I should check? or share?

[Tony]

Hey @scott3,
Another thing we can do is get you updated to the latest odrive version. This has more detailed logging and may be able to provide some additional insight on when odrive is closing, to help narrow down the cause. To do this:

1. Exit odrive
2. Download the latest version from here: Set Up Your odrive
3. Install

Also keep an eye on any crash reports that you see created in the console.

What did the uptime and last commands show you? Did it look like the system was restarting unexpectedly?

[scott3]

New version installed now. Thanks. Hard to tell from the login log what’s what. It’s was up two days, but I initiated the reboot. Prior to that, I don’t recall if I did the reboot or it did it itself. I’m just going to keep an eye it going forward. Pasted the log below for FYI.

scott ttys000 Wed Mar 8 15:22 still logged in
scott ttys000 Tue Mar 7 19:00 - 19:00 (00:00)
scott console Sun Mar 5 16:51 still logged in
reboot ~ Sun Mar 5 16:50
shutdown ~ Sun Mar 5 16:48
scott console Tue Feb 28 09:58 - 16:48 (5+06:50)
scott console Mon Jan 30 09:31 - 01:57 (28+16:26)
reboot ~ Mon Jan 30 09:30
scott ttys000 Thu Jan 19 09:41 - 09:41 (00:00)
scott console Mon Jan 16 16:52 - crash (13+16:38)
reboot ~ Mon Jan 16 16:51
shutdown ~ Mon Jan 16 16:49
scott ttys000 Thu Jan 5 18:13 - 18:13 (00:00)
scott ttys000 Tue Jan 3 15:45 - 15:45 (00:00)
scott ttys000 Tue Jan 3 15:45 - 15:45 (00:00)
scott ttys000 Tue Jan 3 15:38 - 15:38 (00:00)
scott ttys000 Tue Jan 3 09:47 - 09:47 (00:00)
scott console Sat Dec 31 15:37 - 16:49 (16+01:11)
reboot ~ Sat Dec 31 15:37
shutdown ~ Sat Dec 31 12:42
scott console Sat Dec 31 12:39 - 12:42 (00:02)
scott console Thu Dec 29 17:48 - 12:39 (1+18:51)
reboot ~ Thu Dec 29 17:47
shutdown ~ Thu Dec 29 17:38
root console Thu Dec 29 17:37 - shutdown (00:00)
scott console Fri Dec 23 11:54 - 17:37 (6+05:43)
reboot ~ Fri Dec 23 11:53
scott ttys000 Mon Dec 19 11:34 - 11:34 (00:00)
scott ttys000 Mon Dec 19 10:59 - 10:59 (00:00)
scott console Thu Dec 8 12:41 - crash (14+23:12)
reboot ~ Thu Dec 8 12:40
scott console Thu Dec 8 12:39 - crash (00:01)
reboot ~ Thu Dec 8 12:38
scott console Wed Dec 7 09:44 - crash (1+02:53)
reboot ~ Wed Dec 7 09:43
scott console Wed Nov 30 13:16 - 09:43 (6+20:26)
reboot ~ Wed Nov 30 13:15
shutdown ~ Wed Nov 30 13:14
scott console Tue Nov 8 13:58 - 13:14 (21+23:15)
reboot ~ Tue Nov 8 13:57
shutdown ~ Tue Nov 8 13:57
scott ttys000 Wed Nov 2 17:01 - 17:01 (00:00)
scott console Wed Nov 2 17:01 - 13:57 (5+21:55)
scott ttys000 Tue Nov 1 12:16 - 12:16 (00:00)
scott console Wed Oct 26 10:24 - 16:09 (7+05:44)
reboot ~ Wed Oct 26 10:23

[Tony]

Thanks @scott3!
Just ping this thread if it happens again and I can help take a look at things.