Response 403 on initial upload of grive #173

Closed
cwoac opened this Issue May 24, 2013 · 2 comments

Projects

None yet

1 participant

@cwoac
cwoac commented May 24, 2013

Works fine for my machine for the first user, but the second fails with this log:

grive version 0.3.0-pre May 9 2013 13:50:18
current time: 2013-05-24T14:35:11.598Z
config file name "./.grive"
last sync time: 1970-01-01T00:00:00.000Z
Reading local directories
file .grive is ignored by grive
previous change stamp is -1
Synchronizing folders
HTTP GET "https://docs.google.com/feeds/default/private/full/-/folder?max-results=50&showroot=true"
HTTP response 200
folder "./ICRA-UARACIN" is created in remote
folder "./Grants" is created in remote
folder "Schedule" has multiple parents, ignored
folder "./Deborah" is created in remote
folder "./C.V." is created in remote
folder "./Backup" is created in remote
folder "./ICRAWebsite" is created in remote
folder "./Smartpen" is created in remote
folder "./Work" is created in remote
Reading remote server file list
HTTP GET "https://docs.google.com/feeds/default/private/full?showfolders=true&showroot=true"
HTTP response 200
document "Book 8 Notes" is a google document, ignored
document "Ella's Paper List" is a google document, ignored
...
Synchronizing files
sync "." already in sync
sync "./grive" doesn't exist in server, uploading
HTTP POST "https://docs.google.com/feeds/upload/create-session/default/private/full?convert=false" with "
<title>grive</title>"
HTTP response 200
HTTP PUT "https://docs.google.com/feeds/upload/create-session/default/private/full?convert=false&upload_id=AEnB2UouAxfHMthqJoMb_WiEUMy4n4XaoMer-9Qga9YeRc189K3ZZRAmkVQ0hQa9nvKNdKZIZCIrJF1hE7bOHlDHX4hBcIzmug"
HTTP response 403
exception: /media/backup/home/archie/src/grive/libgrive/src/protocol/AuthAgent.cc(174): Throw in function long int gr::AuthAgent::CheckHttpResponse(long int, const string&, const gr::http::Header&)
Dynamic exception type: boost::exception_detail::clone_implgr::http::Error
[gr::expt::BacktraceTag*] = #0 0x812c3ec :0 gr::Exception::Exception()
#1 0x8114a58 :0 gr::http::Error::Error()
#2 0x8123c2b :0 gr::AuthAgent::CheckHttpResponse(long, std::string const&, gr::http::Header const&)
#3 0x812366d :0 gr::AuthAgent::Put(std::string const&, gr::File_, gr::DataStream_, gr::http::Header const&)
#4 0x810ce17 :0 gr::v1::Resource::Upload(gr::http::Agent*, std::string const&, bool)
#5 0x810c754 :0 gr::v1::Resource::Create(gr::http::Agent*)
#6 0x810b207 :0 gr::v1::Resource::SyncSelf(gr::http::Agent*, gr::Json const&)
#7 0x810aed8 :0 gr::v1::Resource::Sync(gr::http::Agent*, gr::DateTime&, gr::Json const&)
#8 0x81104ab :0 boost::mfi::mf3<void, gr::v1::Resource, gr::http::Agent*, gr::DateTime&, gr::Json const&>::operator()(gr::v1::Resource, gr::http::Agent_, gr::DateTime&, gr::Json const&) const
#9 0x810f9ab :0 void boost::_bi::list4boost::arg<1, boost::_bi::valuegr::http::Agent*, boost::reference_wrappergr::DateTime, boost::_bi::valuegr::Json >::operator()<boost::_mfi::mf3<void, gr::v1::Resource, gr::http::Agent*, gr::DateTime&, gr::Json const&>, boost::_bi::list1gr::v1::Resource*& >(boost::_bi::type, boost::_mfi::mf3<void, gr::v1::Resource, gr::http::Agent*, gr::DateTime&, gr::Json const&>&, boost::_bi::list1gr::v1::Resource*&&, int)
#10 0x810edb9 :0 void boost::_bi::bind_t<void, boost::_mfi::mf3<void, gr::v1::Resource, gr::http::Agent*, gr::DateTime&, gr::Json const&>, boost::_bi::list4boost::arg<1, boost::_bi::valuegr::http::Agent*, boost::reference_wrappergr::DateTime, boost::_bi::valuegr::Json > >::operator()gr::v1::Resource*(gr::v1::Resource*&)
#11 0x810e1a2 :0 boost::_bi::bind_t<void, boost::_mfi::mf3<void, gr::v1::Resource, gr::http::Agent*, gr::DateTime&, gr::Json const&>, boost::_bi::list4boost::arg<1, boost::_bi::valuegr::http::Agent*, boost::reference_wrappergr::DateTime, boost::_bi::valuegr::Json > > std::for_each<__gnu_cxx::__normal_iterator<gr::v1::Resource**, std::vector<gr::v1::Resource*, std::allocatorgr::v1::Resource* > >, boost::_bi::bind_t<void, boost::_mfi::mf3<void, gr::v1::Resource, gr::http::Agent*, gr::DateTime&, gr::Json const&>, boost::_bi::list4boost::arg<1, boost::_bi::valuegr::http::Agent*, boost::reference_wrappergr::DateTime, boost::_bi::valuegr::Json > > >(__gnu_cxx::__normal_iterator<gr::v1::Resource**, std::vector<gr::v1::Resource*, std::allocatorgr::v1::Resource* > >, __gnu_cxx::__normal_iterator<gr::v1::Resource**, std::vector<gr::v1::Resource*, std::allocatorgr::v1::Resource* > >, boost::_bi::bind_t<void, boost::_mfi::mf3<void, gr::v1::Resource, gr::http::Agent*, gr::DateTime&, gr::Json const&>, boost::_bi::list4boost::arg<1, boost::_bi::valuegr::http::Agent*, boost::reference_wrappergr::DateTime, boost::_bi::valuegr::Json > >)
#12 0x810afca :0 gr::v1::Resource::Sync(gr::http::Agent*, gr::DateTime&, gr::Json const&)
#13 0x81014d2 :0 gr::v1::State::Sync(gr::http::Agent*, gr::Json const&)
#14 0x81083a7 :0 gr::v1::Drive::Update()
#15 0x80e7f11 :0 Main(int, char**)
#16 0x80e83be :0 main
#17 0xb7165e46 /lib/i386-linux-gnu/i686/cmov/libc.so.6 __libc_start_main
#18 0x80e6dc1 :0 _start

[gr::http::HttpResponseTag_] = 403
[gr::http::UrlTag_] = https://docs.google.com/feeds/upload/create-session/default/private/full?convert=false&upload_id=AEnB2UouAxfHMthqJoMb_WiEUMy4n4XaoMer-9Qga9YeRc189K3ZZRAmkVQ0hQa9nvKNdKZIZCIrJF1hE7bOHlDHX4hBcIzmug
[gr::http::HeaderTag*] = Expect:
Accept:
Authorization: Bearer ya29.AHES6ZRepSG7pBJNecLtFKlvJlZDLkFXN6K-X_8PgrinzGZM
GData-Version: 3.0

I tried removing the created ~/.grieve dir and recreating it, but the same error occured

@cwoac
cwoac commented May 24, 2013

I tried following that link at the end, and I get a blank page with the message 'method not allowed'. This looks similar to issue #171, except I know the version of grieve in use works fine on this machine as I have synced from another account.

@cwoac
cwoac commented May 24, 2013

Okay, figured it out - that account had actually exceeded it's quota. I deleted a couple of files and it's fixed. Probably could do with a thing to detect this and put a clearer warning message on it.

@cwoac cwoac closed this May 24, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment