search

YanshuoH / DejaVu

Complexe events are simple results of primary events which are usually seen but no one cares.
1 stars 2 forks source link

Preparing for a great collection day during the World cup #73

Closed babijo closed 10 years ago

babijo commented 10 years ago

hello @YanshuoH I am Preparing for a great collection day during the World cup (before to after de D-day). Can you help to set up a reliable collection engine for this? Tomorrow I will be at UTT. Can we meet at 11h30 or 15h30? tks

YanshuoH commented 10 years ago

What do you mean a reliable collection engine?

Tomorrow I'll make a move house to Paris, I am not sure the come back time yet.

Does your machine work right now?

babijo commented 10 years ago

now it is almost impossible to launch collections either from the PC or from the hard disk on which I copied the folder DejaVu. I do not know what does not work when everything worked well. On the other hand, the extraction of JSON file still does not, even on E which is a hard drive 1 tera. Another point, looking more closely at the graphs is obtained it is difficult to prover that nodes that are related to participents specified events. Example, the contents of tweets displayed on the graph does not always correspond to events. And that in almost 70% of cases for a graph that I had taken the time to analyze in detail.

Mon PC est on mais je prends une douche et je vais récu^pérer mon fils à l'école. Pourquoi?

YanshuoH commented 10 years ago

Well, have you reinstalled your node.js in your PC? Have you checked your environment variable? You may do a "git clone https://github.com/YanshuoH/DejaVu.git” trying to restart the project. And for export of json file, I don't know yet the reason, check this manual may help: http://docs.mongodb.org/v2.2/reference/mongoexport/ Or give me a screenshot for the error?

Finally about the events, all the tweets I have are from tweets API, If you like we can set a filter (as I'm doing right now, but a filter not very restricted) restricted but I think in this case you won't get anything in the most collections.

I mean, your PC works with node.js right now?

babijo commented 10 years ago

1- re-installation of the project locally on my PC: can you send me a txt file of the whole procedure? Should I remove the whole folder DejaVu before the procedure? 2- I have already sent you send some screenshot in the issue #68. I will do other screenshots if you want if the problem remains. 3- for the last point, I have realised that the connected nodes do not have the same events in their tweets when one attempts to check as depicted in this picture. 2014-07-09_2147

YanshuoH commented 10 years ago
  1. Well it's not command line. Remove your node.js in PC, goto: http://nodejs.org/, download the new version and download, install.
  2. I comment in 68
  3. I understand, but it's you who set up the events with this two words? Why can't connect this two nodes?
babijo commented 10 years ago

@YanshuoH 1. is done But in the cmd something is not ok: see the error:

Microsoft Windows [version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. Tous droits réservés.

C:\Users\birregah>cd/

C:>cd mongodb\bin

C:\mongodb\bin>mongod -dbpath c:\DejaVu\models_asset 2014-07-09T23:40:17.725+0200 [initandlisten] MongoDB starting : pid=7744 port=27 017 dbpath=c:\DejaVu\models_asset 64-bit host=p-birregah 2014-07-09T23:40:17.726+0200 [initandlisten] targetMinOS: Windows 7/Windows Serv er 2008 R2 2014-07-09T23:40:17.726+0200 [initandlisten] db version v2.6.0 2014-07-09T23:40:17.726+0200 [initandlisten] git version: 1c1c76aeca21c5983dc178 920f5052c298db616c 2014-07-09T23:40:17.726+0200 [initandlisten] build info: windows sys.getwindowsv ersion(major=6, minor=1, build=7601, platform=2, service_pack='Service Pack 1') BOOST_LIB_VERSION=1_49 2014-07-09T23:40:17.726+0200 [initandlisten] allocator: system 2014-07-09T23:40:17.726+0200 [initandlisten] options: { storage: { dbPath: "c:\D ejaVu\models_asset" } } 2014-07-09T23:40:17.991+0200 [initandlisten] journal dir=c:\DejaVu\models_asset \journal 2014-07-09T23:40:17.994+0200 [initandlisten] recover : no journal files present, no recovery needed 2014-07-09T23:40:18.077+0200 [initandlisten] streaming Assertion failure isOk() D:\data\mci\git@github.commongodb\mongo.git\mongodb-mongo-v2.6\src\mongo/db/stor age/extent.h 80 2014-07-09T23:40:18.676+0200 [initandlisten] mongod.exe ...\src\mongo\util\st acktrace.cpp(169) mongo::printStackTrace+0x43 2014-07-09T23:40:18.677+0200 [initandlisten] mongod.exe ...\src\mongo\util\lo g.cpp(122) mongo::logContext+0x9c 2014-07-09T23:40:18.677+0200 [initandlisten] mongod.exe ...\src\mongo\util\as sert_util.cpp(115) mongo::verifyFailed+0x14a 2014-07-09T23:40:18.679+0200 [initandlisten] mongod.exe ...\src\mongo\db\stor age\extent_manager.cpp(224) mongo::ExtentManager::getExtent+0x66 2014-07-09T23:40:18.680+0200 [initandlisten] mongod.exe ...\src\mongo\db\stru cture\collection_iterator.cpp(58) mongo::FlatIterator::FlatIterator+0x93 2014-07-09T23:40:18.680+0200 [initandlisten] mongod.exe ...\src\mongo\db\cata log\collection.cpp(137) mongo::Collection::getIterator+0xad 2014-07-09T23:40:18.682+0200 [initandlisten] mongod.exe ...\src\mongo\db\exec \collection_scan.cpp(92) mongo::CollectionScan::work+0xc7 2014-07-09T23:40:18.682+0200 [initandlisten] mongod.exe ...\src\mongo\db\quer y\plan_executor.cpp(91) mongo::PlanExecutor::getNext+0x16b 2014-07-09T23:40:18.683+0200 [initandlisten] mongod.exe ...\src\mongo\db\cata log\database.cpp(319) mongo::Database::clearTmpCollections+0x12d 2014-07-09T23:40:18.685+0200 [initandlisten] mongod.exe ...\src\mongo\db\db.c pp(383) mongo::repairDatabasesAndCheckVersion+0x2b9 2014-07-09T23:40:18.685+0200 [initandlisten] mongod.exe ...\src\mongo\db\db.c pp(730) mongo::_initAndListen+0xae1 2014-07-09T23:40:18.686+0200 [initandlisten] mongod.exe ...\src\mongo\db\db.c pp(773) mongo::initAndListen+0x27 2014-07-09T23:40:18.687+0200 [initandlisten] mongod.exe ...\src\mongo\db\db.c pp(1011) mongoDbMain+0x255 2014-07-09T23:40:18.687+0200 [initandlisten] mongod.exe ...\src\mongo\db\db.c pp(816) wmain+0x35 2014-07-09T23:40:18.689+0200 [initandlisten] mongod.exe f:\dd\vctools\crt_bld \self_64_amd64\crt\src\crt0.c(278) __tmainCRTStartup+0x13b 2014-07-09T23:40:18.690+0200 [initandlisten] kernel32.dll BaseThreadInitThunk+0xd 2014-07-09T23:40:18.691+0200 [initandlisten] streaming 2014-07-09T23:40:18.691+0200 [initandlisten] exception in initAndListen: 0 asser tion D:\data\mci\git@github.commongodb\mongo.git\mongodb-mongo-v2.6\src\mongo/db /storage/extent.h:80, terminating 2014-07-09T23:40:18.692+0200 [initandlisten] dbexit: 2014-07-09T23:40:18.693+0200 [initandlisten] shutdown: going to close listening sockets... 2014-07-09T23:40:18.694+0200 [initandlisten] shutdown: going to flush diaglog...

2014-07-09T23:40:18.694+0200 [initandlisten] shutdown: going to close sockets...

2014-07-09T23:40:18.695+0200 [initandlisten] shutdown: waiting for fs preallocat or... 2014-07-09T23:40:18.695+0200 [initandlisten] shutdown: lock for final commit... 2014-07-09T23:40:18.695+0200 [initandlisten] shutdown: final commit... 2014-07-09T23:40:18.821+0200 [initandlisten] shutdown: closing all files... 2014-07-09T23:40:18.822+0200 [initandlisten] closeAllFiles() finished 2014-07-09T23:40:18.824+0200 [initandlisten] journalCleanup... 2014-07-09T23:40:18.827+0200 [initandlisten] removeJournalFiles 2014-07-09T23:40:19.076+0200 [initandlisten] shutdown: removing fs lock... 2014-07-09T23:40:19.078+0200 [initandlisten] dbexit: really exiting now

C:\mongodb\bin>

babijo commented 10 years ago

@YanshuoH should I remove mongo and reinstall it?

YanshuoH commented 10 years ago

It seems that mongo is ok but something run in your _asset/... try to remove mongo.lock in /_asset/

babijo commented 10 years ago

ça ne marche pas

babijo commented 10 years ago

@YanshuoH en fait la commande mongod -dbpath c:\DejaVu\models_asset ne résiste pas. ça se déconnecte tout seul. du coup ça provoque dans le git shell l'erreur:

birregah@P-BIRREGAH /c/DejaVu (master) $ node server.js connect.multipart() will be removed in connect 3. visit https://github.com/senchalabs/connect/wiki/ connect.limit() will be removed in connect 3.0 Express server listening on port 3000 [Error: failed to connect to [localhost:27017]] [Error: failed to connect to [localhost:27017]] [Error: failed to connect to [localhost:27017]] [Error: failed to connect to [localhost:27017]] [Error: failed to connect to [localhost:27017]] [Error: failed to connect to [localhost:27017]] [Error: failed to connect to [localhost:27017]] [Error: failed to connect to [localhost:27017]]

YanshuoH commented 10 years ago

Je comprend, essaie: http://stackoverflow.com/questions/12985100/exited-mongodb-uncleanly-and-now-unsure-how-to-get-it-running-again

Sachant que ce n'est pas local pour moi je ne sais pas exactement le problème.

babijo commented 10 years ago

@YanshuoH je ne vois pas comment procéder. J'ai tenter des choses mais rien. ça continue toujours. En plus je retrouve un dossier DejaVu dans le dossier DejaVu. Ce qui normalement ne doit pas être le cas. 2014-07-10_0108

YanshuoH commented 10 years ago

Je pense que tu as fait un git clone... Ne te dérange pas ça, on verra bien ensemble.