Gelegentlich treten in Meteor -Nach einem Update – so vielsagende Fehlermeldungen beim Start auf wie
z.B:
J:\Users\username\ticketM>meteor
[[[[[ J:\Users\username\ticketM ]]]]]
=> Started proxy.
=> Exited with code: 8
W20151008-14:44:53.611(2)? (STDERR) J:\Users\username\AppData\Local\.meteor\packages\meteor-tool\1.1.9\mt-os.window
s.x86_32\dev_bundle\server-lib\node_modules\fibers\future.js:278
W20151008-14:44:53.611(2)? (STDERR) at new MongoConnection (packages/mongo/mongo_driver.js:213:1)
W20151008-14:44:53.612(2)? (STDERR) at Object.
W20151008-14:44:53.613(2)? (STDERR) at Socket.
-mongo\1.4.39_1\npm\node_modules\mongodb\lib\mongodb\connection\connection.js:440:22)
W20151008-14:44:53.613(2)? (STDERR) at [object Object].emit (events.js:98:17)
W20151008-14:44:53.613(2)? (STDERR) at [object Object].
kages\npm-mongo\1.4.39_1\npm\node_modules\mongodb\lib\mongodb\connection\connection_pool.js:207:13)
W20151008-14:44:53.613(2)? (STDERR) at [object Object].MongoReply.parseBody (J:\Users\username\AppData\Local\.m
eteor\packages\npm-mongo\1.4.39_1\npm\node_modules\mongodb\lib\mongodb\responses\mongo_reply.js:68:5)
W20151008-14:44:53.613(2)? (STDERR) at [object Object].
kages\npm-mongo\1.4.39_1\npm\node_modules\mongodb\lib\mongodb\connection\server.js:446:20)
W20151008-14:44:53.613(2)? (STDERR) at [object Object].emit (events.js:95:17)
W20151008-14:44:53.612(2)? (STDERR) at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collect
ion_driver.js:4:1)
W20151008-14:44:53.612(2)? (STDERR) at Object.defaultRemoteCollectionDriver (packages/underscore/packages/under
score.js:779:1)
W20151008-14:44:53.612(2)? (STDERR) at new Mongo.Collection (packages/mongo/collection.js:98:1)
W20151008-14:44:53.612(2)? (STDERR) at J:\Users\username\AppData\Local\.meteor\packages\npm-mongo\1.4.39_1\npm\
node_modules\mongodb\lib\mongodb\connection\repl_set\repl_set.js:480:45
W20151008-14:44:53.612(2)? (STDERR) at J:\Users\username\AppData\Local\.meteor\packages\npm-mongo\1.4.39_1\npm\
node_modules\mongodb\lib\mongodb\connection\server.js:393:9
W20151008-14:44:53.613(2)? (STDERR) at Server.Base._callHandler (J:\Users\username\AppData\Local\.meteor\packag
es\npm-mongo\1.4.39_1\npm\node_modules\mongodb\lib\mongodb\connection\base.js:453:41)
W20151008-14:44:53.613(2)? (STDERR) at J:\Users\username\AppData\Local\.meteor\packages\npm-mongo\1.4.39_1\npm\
node_modules\mongodb\lib\mongodb\connection\server.js:488:18
W20151008-14:44:53.612(2)? (STDERR) – – – – –
W20151008-14:44:53.559(2)? (STDERR)
W20151008-14:44:53.611(2)? (STDERR) throw(ex);
W20151008-14:44:53.612(2)? (STDERR) at new AccountsServer (accounts_server.js:16:5)
W20151008-14:44:53.611(2)? (STDERR) ^
W20151008-14:44:53.611(2)? (STDERR) Error: No valid replicaset instance servers found
W20151008-14:44:53.611(2)? (STDERR) at Object.Future.wait (J:\Users\username\AppData\Local\.meteor\packages\met
eor-tool\1.1.9\mt-os.windows.x86_32\dev_bundle\server-lib\node_modules\fibers\future.js:398:15)
W20151008-14:44:53.612(2)? (STDERR) at AccountsServer.AccountsCommon (accounts_common.js:23:18)
W20151008-14:44:53.612(2)? (STDERR) at Package (globals_server.js:5:12)
W20151008-14:44:53.612(2)? (STDERR) at J:\Users\username\ticketM\.meteor\local\build\programs\server\packages\a
ccounts-base.js:1813:4
Batchvorgang abbrechen (J/N)? ^C
Muss irgenwas mit Mongo zu tun haben.
Was, wo und warum nicht läuft … sehe ich nicht. Da ich nicht weiß wo ich suchen muss, die DB Instanz auch nicht läuft, blieb lediglich ein:
meteor reset
Alles lief wieder, leider werden so die Daten gelöscht. Es war noch nichts Produktives, aber das kann es natürlich nicht sein !