uwsgi-core

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
jmeyer
Messages: 43
Registration: March 30, 2015 - 3:15 PM

May 18, 2015 - 1:54 PM

Good morning,

I get the following error.
I updated to version 1.2 this morning but I don't know if that's related.

Code: Select all

May 18 13:52:27 debian kernel: [  617.824017] Out of memory: Kill process 3263 (uwsgi-core) score 108 or sacrifice child
May 18 13:52:27 debian kernel: [  617.824333] Killed process 3263 (uwsgi-core) total-vm:160272kB, anon-rss:54936kB, file-rss:24kB
Thanks in advance.
High
jmeyer
Messages: 43
Registration: March 30, 2015 - 3:15 PM

May 18, 2015 - 3:56 PM

After some testing, with 1GB or 2GB of RAM, the problem persists.
The previous message is due to memory saturation at the very beginning of the machine's startup.
If I stop the waptserver service, the memory is freed.
High
jmeyer
Messages: 43
Registration: March 30, 2015 - 3:15 PM

May 19, 2015 - 08:55

New info, I have about 15 instances of uwsgi-core which take up about 5% of the RAM each.
Is it possible to reduce or limit the number of simultaneous instances?
Untitled.png
Untitled.png (93.87 KB) Viewed 6531 times
High
User avatar
Yvan Karmouta
Messages: 34
Registration: June 18, 2014 - 10:09
Contact :
Contact Yvan Karmouta

May 20, 2015 - 09:09

Good morning,
How many Wapt customers do you have?
At the end of your update, did you restart the postconf script?

Code: Select all

python /opt/wapt/waptserver/scripts/postconf.py
Yvan Karmouta - Tranquil IT Systems
Feel free to leave us your opinion on Wapt in the forum, or to answer our questionnaires :).
High
jmeyer
Messages: 43
Registration: March 30, 2015 - 3:15 PM

May 20, 2015 - 11:02

Hello,
I have between 250 and 300 WAPT clients.
I just restarted the script, but I don't think I ran it after updating from 1.1 to 1.2 as indicated in the documentation.
High
jmeyer
Messages: 43
Registration: March 30, 2015 - 3:15 PM

May 21, 2015 - 08:47

I just migrated to a new server where I installed 3GB of RAM and 4 cores.
The problem seems to be solved.
High
Locked

Return to "WAPT Server"


  • To go further with WAPT