Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transport endpoint is not connected #60

Closed
ovel2clock opened this issue Apr 4, 2014 · 7 comments
Closed

Transport endpoint is not connected #60

ovel2clock opened this issue Apr 4, 2014 · 7 comments

Comments

@ovel2clock
Copy link

First off, I love this! This is exactly what I was looking for for Plex.

I was able to successfully connect to my google drive using the steps listed out on GitHub and I was able to upload/download files.However, after some time, it drops the connection telling me the transport endpoint is not connected. I've tried remounting with no luck.

Here's what gdfuse.log shows :
[0.000638] TID=0: Setting up default filesystem...
[0.000676] TID=0: Loading configuration from /home/user/.gdfuse/default/config...done
Saving configuration in /home/user/.gdfuse/default/config...done
[0.001157] TID=0: Loading application state from /home/user/.gdfuse/default/state...done
Current version: 0.5.3
Setting up cache db...done
Setting up CURL...done
Refresh token already present.
[0.004306] TID=0: Starting filesystem /mnt/gdrive/
[0.015072] TID=0: init_filesystem
[35.449524] TID=0: getattr /
Loading metadata from db...not valid
Refreshing metadata...Refreshing access token...fail (error_code=Exception)
Error refreshing access token (try=0):
Exception:GaeProxy.ServerError("error_code Exception")
Backtrace:
fail (error_code=Exception)
Error refreshing access token (try=1):
Exception:GaeProxy.ServerError("error_code Exception")
Backtrace:
fail (error_code=Exception)

If I remove the .gdfuse directory and start over, it works again until it drops again after some time.

Any ideas? Thanks in advance!

@astrada
Copy link
Owner

astrada commented Apr 4, 2014

Are you using your custom client_id and client_secret? If it is the case, you should check the config file and look for the keys client_id and client_secret. They should contain your values. If they are empty you will get that kind of error.

@ovel2clock
Copy link
Author

@astrada That was it. Thanks for the help!

BTW, I did the headless install and it didn't update client_id and client_secret within the config file. Not sure if it's intended to be like that or if it's a bug.

Regardless, awesome utility!

@astrada
Copy link
Owner

astrada commented Apr 5, 2014

It's probably a bug. I will look into it.

@astrada astrada added the bug label Apr 5, 2014
@markginter31
Copy link

Ubuntu 14.04 32bit (using repository) - in Nautilus I get the Transport endpoint not connected. I have all info filled in in the config file. Had to do a headless install b/c it kept segfaulting. Finished setup via headless - but now it segfaults when it gets to the refreshing metadata point.

[0.000311] TID=0: Setting up iu12gdrive filesystem...
[0.000357] TID=0: Loading configuration from /home/mark/.gdfuse/iu12gdrive/config...done
Saving configuration in /home/mark/.gdfuse/iu12gdrive/config...done
[0.000668] TID=0: Loading application state from /home/mark/.gdfuse/iu12gdrive/state...done
Current version: 0.5.3
Setting up cache db...done
Setting up CURL...done
Refresh token already present.
[0.003806] TID=0: Starting filesystem iu12gdrive
[0.014587] TID=0: init_filesystem
[0.014733] TID=0: getattr /.Trash
Loading metadata from db...not found
Refreshing metadata...

and then segfault in the terminal -- shows it's connected in nautilus but gives transport error when I click on the folder.

@astrada
Copy link
Owner

astrada commented Apr 19, 2014

It looks like it's segfaulting when fetching some HTTPS urls. I'm investigating this problem. See issue #54.

@astrada
Copy link
Owner

astrada commented Jan 16, 2015

Closing as duplicate of #106.

@astrada astrada closed this as completed Jan 16, 2015
@JoseFMP
Copy link

JoseFMP commented Oct 2, 2018

I do not see why it's duplicated of #106.

In any case, it's still happening. Ubuntu 18.04, google-drive-ocamlfuse, version 0.7.0
Any workarounds? It's a pity as this was the only decent solution to sync with google drive from ubuntu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants