Anita, It sounds like there are two potentially separate issues here.
For the first item related to Riak CS - was there already an admin user created? are all (mb, rb, put, get) operations returning the 403 "The AWS Access Key Id you provided does not exist in our records." error? The console logs from Riak CS or Stanchion may reveal more relevant detail. I'd be happy to look over the configs and logs for you if you want to zip them all up and send them directly. The invalid hint files should not prevent Riak from returning requests so might be a red herring with regard to the above error. Cheers, On Mon, Dec 30, 2013 at 2:03 AM, Anita Wong <[email protected]>wrote: > Hi, > > I’m running RIak with Riak-CS for some time already. > > Today when I tried to access it, I found that the it returns > "The AWS Access Key Id you provided does not exist in our records." > > I tried to use Riak-CS Control to look at the user list, but it returned > that there’s no data, even if I called > > curl -H 'Content-Type: application/json' \ > -X POST http://localhost:8080/riak-cs/user \ > --data '{"email":"[email protected]", "name":"admin user"}' > > as suggested from the website. > > The objects uploaded directly to Riak (without Riak-CS) can still be > accessed, only those through RIak-CS failed. > > I also found crash.log in RIak, Stanchion and Riak-CS, the one in Riak > seems to be the problem: > 2013-12-30 15:36:38 =ERROR REPORT==== > Hintfile > '/vol1/riak/bitcask/799258707915337533392640142891717276374338109440/1.bitcask.hint' > invalid > 2013-12-30 15:36:39 =ERROR REPORT==== > Hintfile '/vol1/riak/bitcask/0/1.bitcask.hint' invalid > 2013-12-30 15:36:39 =ERROR REPORT==== > Hintfile > '/vol1/riak/bitcask/91343852333181432387730302044767688728495783936/1.bitcask.hint' > invalid > 2013-12-30 15:36:39 =ERROR REPORT==== > Hintfile > '/vol1/riak/bitcask/319703483166135013357056057156686910549735243776/1.bitcask.hint' > invalid > 2013-12-30 15:36:39 =ERROR REPORT==== > Hintfile > '/vol1/riak/bitcask/182687704666362864775460604089535377456991567872/1.bitcask.hint' > invalid > 2013-12-30 15:36:39 =ERROR REPORT==== > Hintfile > '/vol1/riak/bitcask/45671926166590716193865151022383844364247891968/1.bitcask.hint' > invalid > 2013-12-30 15:36:39 =ERROR REPORT==== > Hintfile > '/vol1/riak/bitcask/296867520082839655260123481645494988367611297792/1.bitcask.hint' > invalid > 2013-12-30 15:36:39 =ERROR REPORT==== > Hintfile > '/vol1/riak/bitcask/365375409332725729550921208179070754913983135744/1.bitcask.hint' > invalid > 2013-12-30 15:36:39 =ERROR REPORT==== > Hintfile > '/vol1/riak/bitcask/159851741583067506678528028578343455274867621888/1.bitcask.hint' > invalid > 2013-12-30 15:36:39 =ERROR REPORT==== > …. > > Any suggestion on how to solve or prevent this? Thanks a lot. > > *Anita WONG* > > > _______________________________________________ > riak-users mailing list > [email protected] > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
