Dear Team, i got my cloud instance to work. i disabled journals in the mongo start config file. however, i still see only 4GB of disk space instead of 40GB like announced in the lab. I am running on Spain 2 by the way. However, i have another issue since i can not connect to my instance via a context broker query. i am using the simple example script from the fiware docu. i created a context element locally on the instance via localhost. it works and is fine exactly as described in the room example of the docu. however, i assigned a floating ip and when i use it to query the context broker from outside, i get: > curl: (7) Failed to connect to 130.206.114.179 port 1026: Operation timed out > No JSON object could be decoded i attached my very simple example script which contains my ip. i suspect that i have to use some kind of authentication? i have a keypair and it works fine for the ssh login. but i can’t use it for the query script, right? thanks again for your help. please see my example attached. cheers lars > On 17 Apr 2015, at 00:05, Lars Buntemeyer <larsbuntemeyer at gmail.com <mailto:larsbuntemeyer at gmail.com>> wrote: > > dear fiware team, > thanks for your great help so far!! > I have to bother you again, since i try starting the context broker in my own instance. i deployed the instance successfully and also installed the orion context broker and mongodb successfully. However, the instance seems to have much less disc space than suggested in the cloud where i deployed it. This troubles the mongdodb since it says: > >> 2015-04-17T00:53:39.719+0300 [initandlisten] ERROR: Insufficient free space for journal files >> 201 2015-04-17T00:53:39.719+0300 [initandlisten] Please make at least 3379MB available in /var/lib/mongo/journal or use —smallfiles > > df -h gives me > >> Filesystem Size Used Avail Use% Mounted on >> /dev/vda1 4.8G 3.4G 1.3G 74% / >> tmpfs 1.9G 80K 1.9G 1% /dev/shm > > Since i actually launched the instance with the “medium flavor”, the lab says: > >> RAM: 4096MB >> VCPUs: 2 VCPU >> Disk: 40GB > > Do you any idea here? Thanks a lot! > > cheers > lars -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150417/db918067/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: get_room.sh Type: application/octet-stream Size: 333 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150417/db918067/attachment.obj> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-lab-help/attachments/20150417/db918067/attachment-0001.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy