MongoDB crashes on startup

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
asder
Messages: 4
Registration: August 10, 2017 - 6:21 PM

August 10, 2017 - 6:29 PM

Good morning,
I'm testing Wapt on a test Debian 9 server
The admin console on a Windows 7 client installed correctly, but "unable to connect to the MongoDB database" error occurred

Checking the server's syslog, I find:
Aug 10 17:59:20 srvglpi systemd[1]: Started An object/document-oriented database.
Aug 10 17:59:20 srvglpi kernel: [ 3303.161739] traps: mongod[1675] trap invalid opcode ip:80591a8f sp:bf84b0e0 error:0
Aug 10 17:59:20 srvglpi kernel: [ 3303.161749] in mongod[80084000+1ab6000]
Aug 10 17:59:20 srvglpi systemd[1]: mongodb.service: Main process exited, code=killed, status=4/ILL
Aug 10 17:59:20 srvglpi systemd[1]: mongodb.service: Unit entered failed state.
Aug 10 17:59:20 srvglpi systemd[1]: mongodb.service: Failed with result 'signal'.
I tried what's suggested in the "common problems" section, but nothing works...
Compatibility issue with Debian 9?
Thank you for your feedback
User avatar
agauvrit
WAPT Expert
Messages: 238
Registration: Nov 17, 2016 - 10:25
Location: Nantes
Contact :

August 11, 2017 - 10:45

Hello, which version of WAPT are you using? 1.3.13?

Are there any other services already installed on this server? GLPI, judging by the machine name?

We'll look into it on our end.
asder
Messages: 4
Registration: August 10, 2017 - 6:21 PM

August 11, 2017 - 10:59

yes 1.3.13.0
I reinstalled it on an Ubuntu server that I just installed from scratch (so no other services were present)
=> same
Aug 11 10:52:40 wapt kernel: [ 2852.653659] traps: mongod[5561] trap invalid opcode ip:84ecaef sp:bfd2df50 error:0
Aug 11 10:52:40 wapt kernel: [ 2852.653668] in mongod[8048000+1a4d000]
Aug 11 10:52:41 wapt systemd[1]: mongodb.service: Main process exited, code=dumped, status=4/ILL
Aug 11 10:52:41 wapt systemd[1]: mongodb.service: Unit entered failed state.
Aug 11 10:52:41 wapt systemd[1]: mongodb.service: Failed with result 'core-dump'.
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

August 11, 2017 - 11:17 PM

No problem on my end with Debian 9.

What would be interesting to know is if the Bose MongoDB server accepts starting before your system is registered (with no files).
asder
Messages: 4
Registration: August 10, 2017 - 6:21 PM

August 13, 2017 - 10:09 PM

I tried again with a newer CPU and more RAM, and it works!
So it was definitely a hardware issue.
Thanks for the help,
Thierry.
Locked