number of processes?

[HansR]

I do not look very often at htop on my rpi, I have pretty much confidence in continuous running of CMX.
But today I did and I suddenly saw much more processes than I was used to.

Is this correct (i.e. is this the consequence of version 3.24)?

Schermafbeelding 2023-03-18 194444.png

[freddie]

My installation has a constant 25 processes, using very few resources. I'm happy with that, provided it continues to remain constant.

[Nossie]

This looks wrong,

I would restart but I wouldn't expect it to do this.

[HansR]

@Freddie: Yes, that's about what I expect... now the question: where do the additional processes come from?
@Nossie: Agree it looks wrong. My system restarts automatically every Monday morning at around @02h00 but now the questions: where does this come from?

[mcrossley]

My live install is running with 24/25 processes as well - that does not use any uploads though.

We are going to have to find what is common in the configs that are creating these abandoned processes.

Most obvious is using PHP upload as that is where the major changes have been.

[HansR]

OK. What do you need to know? Upload, nr of uploads? Copies etc... Short : I use PHP upload, switched off the copies and reduced the downloads as much as possible. That is about all I changed. when going to 3.24.

If you need the inifile let me know. We'll probably need a table to enter all configs and compare.

[AndyKF650]

Hi there

I did a clean reinstall and reboot this afternoon and after a few hours looking at HTOP my process number is about 50. Like Hans I am running CMX and CUtils on a RPI 4 with php uploads to my web site.

Please let me know if you need more detail.

[mcrossley]

OK, how about trying to correlate the increasing thread count with the MXdiags log file and see if the increases coincide with any errors?

So, switch on debug logging in CMX.

Then schedule a task with CRON say every 30 seconds with a couple of command lines like (or a script containing these)...

Code: Select all

echo "`date "+%FT%T"` `ps auxH | grep "CumulusMX.exe" | egrep -v "grep" | wc -l`" >> /tmp/processlog.txt

and

Code: Select all

sleep 30; echo "`date "+%FT%T"` `ps auxH | grep "CumulusMX.exe" | egrep -v "grep" | wc -l`" >> /tmp/processlog.txt

[freddie]

For my setup, I do no uploads - just a single local file copy (moon image) which is accessed from my website via Apache proxying. I save all data to a local database that is then synchronised to my web-facing database, which then feeds my website.

So - just the one local copy for me. No FTP or PHP upload.

[HansR]

OK, I have those lines in a crontab procedure:

Code: Select all

0-59/1 * * * * ./TryProcesses.sh

And TryProcesses is:

Code: Select all

#!/bin/bash
echo "`date "+%FT%T"` `ps auxH | grep "CumulusMX.exe" | egrep -v "grep" | wc -l`" >> /tmp/processlog.txt
sleep 30;
echo "`date "+%FT%T"` `ps auxH | grep "CumulusMX.exe" | egrep -v "grep" | wc -l`" >> /tmp/processlog.txt

CMX runs with debug on.

I'll get back with the output.

[Gkirk]

Update on 20230321:

After running a bit over 2 days, Cumulus now logging 20% CPU busy:

Noted that there are now 7 conhost.exe processes in existence. They are spawned from the cmd.exe process according to multiple sources via google. There may be a relation between the CPU consumption and the number of cmdhost.exe processes running. Will let it spin another day and report back.

PREVIOUSLY:

cumulusmxbug.png

Cumulusmx chews 84% of the cpu after running slightly more than a day. Noticed it started with build 3234. Did not think to look at process details but will do so and report any extra that I find. Restarting brings cpu usage back to normal for a day or so.



Processor   Intel(R) Core(TM) i5-6440HQ CPU @ 2.60GHz 2.60 GHz
Installed RAM     16.0 GB (15.9 GB usable)
System type 64-bit operating system, x64-based processor


Edition     Windows 11 Pro Insider Preview
Version     22H2
Installed on      ‎3/‎10/‎2023
OS build  25314.1010  



Startup in cmd window

c:\cumulusMX>dir cum*
Volume in drive C has no label.
Volume Serial Number is 44EB-51EF

Directory of c:\cumulusMX

03/10/2023 02:15 PM 20,377 Cumulus.ini
01/12/2023 06:33 PM <DIR> CumulusMX
03/11/2023 11:48 AM 2,026,496 CumulusMX.exe
03/11/2023 11:48 AM 2,680 CumulusMX.exe.config
3 File(s) 2,049,553 bytes
1 Dir(s) 65,990,639,616 bytes free

c:\cumulusMX>cumulusmx
Cumulus MX v.3.24.1 build 3234
Working Dir: c:\cumulusMX\

Cumulus running at: http://localhost:8998/
http://100.96.1.78:8998/
http://192.168.1.156:8998/

Open the admin interface by entering one of the above URLs into a web browser.

Today.ini = data\today.ini
Last update=2023-03-15T15:20:00
You are not running the latest version of Cumulus MX, build 3235 is available.
Connected to station
3/15/2023 3:24:58 PM
Type Ctrl-C to terminate
Downloading Archive Data
- processed 100%
Downloading Archive Data
Connecting real time FTP
Normal running
Cumulus terminating
Cumulus stopped

c:\cumulusMX>cumulusmx
Cumulus MX v.3.24.2 build 3235
Working Dir: c:\cumulusMX\

Cumulus running at: http://localhost:8998/
http://100.96.1.78:8998/
http://192.168.1.156:8998/

Open the admin interface by entering one of the above URLs into a web browser.

Today.ini = data\today.ini
Last update=2023-03-16T08:20:00
Connected to station
3/16/2023 8:32:22 AM
Type Ctrl-C to terminate
Downloading Archive Data
- processed 100%
Downloading Archive Data
- No Archive data available
Connecting real time FTP
Normal running
Cumulus terminating
Cumulus stopped

[HansR]

Attached the results until 22h50. There is a reboot scheduled at 02h00 After that a CMX restart daily at 9h05.

[HansR]

Results from 08h10 this morning: more processes and errors in the log so contains probably more info

[rogerthn]

Still using SFTP and still 21 lines as below since start 2023-03-15 14:45:41

Code: Select all

ps kstart_time auxH | grep "CumulusMX.exe" | grep -v grep ;ps kstart_time auxH | grep "CumulusMX.exe" | grep -v grep | wc -l
root     2436929  0.0  0.1  15044  4520 pts/0    S+   Mar15   0:00 sudo mono CumulusMX.exe -debug
root     2436930  0.0  5.8 1443704 227184 pts/0  Sl+  Mar15   0:38 mono CumulusMX.exe -debug
root     2436930  0.0  5.8 1443704 227184 pts/0  Sl+  Mar15   0:44 mono CumulusMX.exe -debug
root     2436930  0.0  5.8 1443704 227184 pts/0  Sl+  Mar15   0:14 mono CumulusMX.exe -debug
root     2436930  0.0  5.8 1443704 227184 pts/0  Sl+  Mar15   0:03 mono CumulusMX.exe -debug
root     2436930  4.0  5.8 1443704 227184 pts/0  Sl+  Mar15 278:49 mono CumulusMX.exe -debug
root     2436930  0.0  5.8 1443704 227184 pts/0  Sl+  Mar15   0:32 mono CumulusMX.exe -debug
root     2436930  0.0  5.8 1443704 227184 pts/0  Sl+  Mar15   2:13 mono CumulusMX.exe -debug
root     2436930  0.1  5.8 1443704 227184 pts/0  Sl+  Mar15  12:29 mono CumulusMX.exe -debug
root     2436930  0.0  5.8 1443704 227184 pts/0  Sl+  Mar15   3:03 mono CumulusMX.exe -debug
root     2436930  0.0  5.8 1443704 227184 pts/0  Sl+  Mar15   0:18 mono CumulusMX.exe -debug
root     2436930  0.1  5.8 1443704 227184 pts/0  Sl+  Mar15  12:34 mono CumulusMX.exe -debug
root     2436930  0.1  5.8 1443704 227184 pts/0  Sl+  Mar15  12:28 mono CumulusMX.exe -debug
root     2436930  0.1  5.8 1443704 227184 pts/0  Sl+  Mar15  12:24 mono CumulusMX.exe -debug
root     2436930  0.1  5.8 1443704 227184 pts/0  Sl+  Mar15  12:26 mono CumulusMX.exe -debug
root     2436930  0.1  5.8 1443704 227184 pts/0  Sl+  Mar15  12:34 mono CumulusMX.exe -debug
root     2436930  0.1  5.8 1443704 227184 pts/0  Sl+  Mar15  12:33 mono CumulusMX.exe -debug
root     2436930  0.1  5.8 1443704 227184 pts/0  Sl+  Mar15  12:31 mono CumulusMX.exe -debug
root     2436930  0.1  5.8 1443704 227184 pts/0  Sl+  Mar15  11:49 mono CumulusMX.exe -debug
root     2436930  0.1  5.8 1443704 227184 pts/0  Sl+  Mar15  11:51 mono CumulusMX.exe -debug
root     2436930  0.1  5.8 1443704 227184 pts/0  Sl+  Mar15  11:55 mono CumulusMX.exe -debug
21

PS
My WS80 is dead since 2023-03-18 04:25, replacement orded

[AndyKF650]

Hi there

Having run the debug logging for a 15mins this morning all seems to be quite normal with no errors. The number of CMX processes is constant at 51.

I have attached the MXDiags file which shows the debug lines from 2408 at 2023-03-20 07:38. Also attached is the results of Hans' process monitoring script.

I am not sure if a long run of debug monitoring will show much more info but please let me know if you need any further info.