Hudi Ilfeld's questions

S.O.S!! I had my t2.micro with Bitnami Parse image running for a good while.

everything was fun and games until I needed to upgrade to t2.medium.

In order to do so I cloned my server to an AMI image. Then I launched my brand new t2.medium from my AMI image. I woke up in the morning just to discover that my old server is giving me the following error when I run the command mongod:

2019-07-18T07:07:09.667+0000 I CONTROL  [initandlisten] MongoDB 
starting : pid=1696 port=27017 dbpath=/data/db 64-bit host=ip-172-31-37-229
2019-07-18T07:07:09.667+0000 I CONTROL  [initandlisten] db version v3.0.9
2019-07-18T07:07:09.667+0000 I CONTROL  [initandlisten] git version:
20d60d3491908f1ae252fe452300de3978a040c7
2019-07-18T07:07:09.667+0000 I CONTROL  [initandlisten] build info:
Linux build4.ny.cbi.10gen.cc 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 
21:39:27 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49
2019-07-18T07:07:09.667+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2019-07-18T07:07:09.667+0000 I CONTROL  [initandlisten] options: {}
2019-07-18T07:07:09.756+0000 I STORAGE  [initandlisten] exception in 
initAndListen: 29 Data directory /data/db not found., terminating
2019-07-18T07:07:09.756+0000 I CONTROL  [initandlisten] dbexit:  rc: 100

First I thought there duplicated t2.medium server is causing issues so I terminated it. but still nothing changed on my old t2.micro. and I cannot locate my old mongodb data!!!!

My question is: is this a result due to a side affect that might have being caused due to the AMI image process or it's something else. perhaps an attack on my server!!!!!

I am in great trouble. Any help will be much appreciated!!!

T.I.A

I am well aware of how to upload .p12 cert for iOS push notifications - via Heroku or Back4App. However my Parse server is hosted on AWS ec2 instance with Bitnami image. Hence I can only interact with my server via my Terminal. I tried uploading the PFX (.p12) from my local machine via scp something like this:

scp -i /Path/To/My/Certificates.p12 ubuntu@server_ip: /home

but I am receiving the following error in Terminal:

Load key "/Path/To/My/Certificates.p12": invalid format ubuntu@server_ip: Permission denied (publickey).

There is unfortunately poor documentation regarding how to upload p12 files without GUI's like Back4App/Heroku.

So I would be very glad if someone could assist me on this matter.

T.I.A

As the title implies, I need to copy db from ec2 instance with bitnami image that has mongodb pre-installed with version 3.0.9 , to new bitnami ec2 instance that has mongodb version 3.6.8 pre-installed.

I first used:

db.copyDatabase("my_db", "my_db", "000.00.00.000", "root", "xxxxxxxxxx")

but then I received the following output:

{
"ok" : 0,
"errmsg" : "Server min and max wire version are incompatible (0,3) with client min wire version (6,6)"
}

Now, from what I understand, This messages is implying that mongo cannot copy the db since they are 2 different mongo versions.

So from the 2 cent knowledge I have on this matter, I came to the understanding that I need to upgrade my first ec2 instance - mongodb(3.0.9) to be compatible with the mongo db I need to copy to i.e 3.6.8.

I have followed the set of instructions in the mongo docs here to gradually update to 3.2 and then 3.4 etc.. but I although I completed all instructions, my mongo db version remains 3.0.9

Im assuming that it is related to the bitnami infrastructure and the way they have there mongodb installed, but I cannot point to the problem.

I am really stuck on this matter. (perhaps I don't need to upgrade mongo db and there is a workaround etc.. because I am banging my head in the wall)

T.I.A

I am using parse server as a BAAS for my android app. Everything Is working like a charm, except, when I use the app as a single user intensely I.E. if I send several requests in a very small span of time (refreshing the data many times quickly) from my android client to the parse server, the server freezes. and I get a message back from my cloud function saying: "i/o failure".

I am not getting any info in my parse.logs file related to the issue besides the "i/o failure" message on client-side I would be more then happy to understand the cause for this issue. and I how to resolve it.

Environment Setup

Server

parse-server version: 1.17.3

Operating System: Ubuntu (Bitnami image)

remote server? AWS

Database

MongoDB version: v3.0.9

Localhost