to retain space on the vm, I was deleting tmp data that was filling up in this directory:
/file_store/cumulus/posixdata/f/
however... there is apparently some tmp file related to the emoticons and since I deleted that, they are now all broken?! and the people need their emoticons. help!
2017-03-17 17:14:18,352 - 4087 - INFO - path /files/img/emoticons/smile.png
2017-03-17 17:14:18,352 - 4087 - INFO - path /files/img/emoticons/smile.png bucket files object img/emoticons/smile.png
2017-03-17 17:14:18,354 - 4087 - ERROR - <?xml version="1.0" ?><Error><Code>InternalError</Code><Message>We encountered an internal error. Please try again.</Message><Resource>/files/img/emoticons/smile.png</Resource><RequestId>27978cb80b3511e7a2da005056afbc77</RequestId></Error>
2017-03-17 17:14:18,354 - 4087 - ERROR - Stack trace
2017-03-17 17:14:18,354 - 4087 - ERROR - ===========
2017-03-17 17:14:18,354 - 4087 - ERROR - Traceback (most recent call last):
File "/opt/cumulus/cb/pycb/cumulus.py", line 180, in process_event
self.allowed_event(request, user, requestId, rPath)
File "/opt/cumulus/cb/pycb/cumulus.py", line 194, in allowed_event
cbR.work()
File "/opt/cumulus/virtualenv/local/lib/python2.7/site-packages/pycb/cbRequest.py", line 415, in work
obj = self.bucketIface.get_object(data_key)
File "/opt/cumulus/virtualenv/local/lib/python2.7/site-packages/pycb/cbPosixBackend.py", line 76, in get_object
obj = cbPosixData(data_key, "r")
File "/opt/cumulus/virtualenv/local/lib/python2.7/site-packages/pycb/cbPosixBackend.py", line 128, in __init__
self.file = open(self.fname, access)
IOError: [Errno 2] No such file or directory: '/file_store/cumulus/posixdata/f/tmpQlABn5files__img__emoticons__smile.png'
got this issue resolved.
was sent a .gz files of the missing files from a different server and just renamed those to match what the logs were complaining about as missing.
yeap yeap. I have a ticket going and still waiting to get this resolved.
I am hoping there is just some tarball I can restore on the server :/
will definitely update here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Cyrus, have you submitted a support ticket to our support team yet? I'd suggest starting there. And then perhaps when the problem is resolved, either you or the support team can add an answer as to how it was resolved in case anyone else ever runs into this problem and finds this question. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.