Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mongo memory server will not stay connected #475

Closed
code4fun907 opened this issue May 27, 2021 · 14 comments
Closed

Mongo memory server will not stay connected #475

code4fun907 opened this issue May 27, 2021 · 14 comments
Labels
Needs More Information question stale This Issue is outdated and will likely be closed if no further comments are given

Comments

@code4fun907
Copy link

Versions

  • NodeJS: 14.17.0
  • mongodb-memory-server-*: 6.9.6
  • mongodb: none
  • mongoose: 5.10.19
  • system: Windows

package: mongo-memory-server

What is your question?

Im having some real trouble running mongodb memory server on my machine. because Ive already wrote out this question on stackoverflow a few days ago and it still after being seen by almost 50 people remains unsolved I thought I would come here. here is the link to that specific stackoverflow question https://stackoverflow.com/questions/67699988/mongo-memory-server-is-not-starting-at-all

(first time making a github issue so if I did anything wrong im sorry!)

@hasezoey
Copy link
Member

(first time making a github issue so if I did anything wrong im sorry!)

next time, please include the full question instead of just an link to stackoverflow

PS: if it really is just an question, then posting it in discussions is better (will move if it comes to this)

@hasezoey
Copy link
Member

btw, did you already test an 7.0.0-beta.x version?

@hasezoey
Copy link
Member

i looked at the stackoverflow issue, where in the comments it was suggested it was an permissions error, but from what i can tell:

  • the binary is installed correctly
  • the temporary folder is created and can be used

but i also saw that the instance is exiting with code 3221225781 and no extra error logs, but from searching, it seems like this is related to missing libraries (but without error logs, i dont know what libraries are missing)

please try if the same behavior is on 7.0.0-beta.x (the latest beta please) and post the full debug log
Note: 7.0.0 has breaking changes and the migration guide can be found here (it includes the most important changes)

@code4fun907
Copy link
Author

alright I will try this 7.0.0-beta.x version now and come back with results if it works, also thanks for the advice about haha I just did not want to rewrite the entire thing

@hasezoey
Copy link
Member

also thanks for the advice about haha I just did not want to rewrite the entire thing

if the stackoverflow question is formatted correctly, it is basically an copy-paste into here (in the section What is your question?) and still filling out the Versions section

@eric-burel
Copy link

It seems to be related to using Windows, we have the same problem on a windows machine as well.

@hasezoey
Copy link
Member

hasezoey commented Jun 4, 2021

@eric-burel did you already try the beta like mentioned earlier in this issue? and if you hit the same error, could you provide the full debug log while using the beta?

@eric-burel
Copy link

eric-burel commented Jun 4, 2021

We're on it I'll keep you informed on the result, thanks! It's an open source project so if it still doesn't work I'll share a repro.
Edit: PR where you can reproduce the error by installing and running (yarn install; yarn run build; yarn run test;) the tests on Windows: VulcanJS/vulcan-npm#31

@Timi-Duban

This comment has been minimized.

@hasezoey

This comment has been minimized.

@Timi-Duban

This comment has been minimized.

@hasezoey

This comment has been minimized.

@github-actions
Copy link

Marking Issue as stale, will be closed in 7 days if no more activity is seen

@github-actions github-actions bot added the stale This Issue is outdated and will likely be closed if no further comments are given label Dec 20, 2021
@github-actions
Copy link

Closing Issue because it is marked as stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs More Information question stale This Issue is outdated and will likely be closed if no further comments are given
Projects
None yet
Development

No branches or pull requests

4 participants