Procon crashes

[TonyOffermans]

Hi,
I run my own layer on a VM (3 cores, 8GB) and my SQL database is also running on this VM. I also have Ty_ger07's stats page running on another machine. I have some issues with this setup. A few times a day (although some days it runs fine), Procon will crash or start looping. On the VM I find it 'No Longer Works' or it is unresponsive using 98% CPU. It is fine after restart. I also see HD activity spiking 100% for prolonged periods but unable to find the process responsible (I suspect XAMPP MySQL but it does not show in task manager).

Nothing else is running on the VM. I am looking for options to debug the crashes. Any advice? Is it better to run the MySQL on a different server? Any experiences with the stats page being attacked causing MySQL to refuse connections (I had this yesterday, my plugins got disabled and were unable to connect (MySqlException (0x80004005): Host '195.201.183.204' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts') ? I have no clue how this situation could arise...
My hat off for your thoughts, thank you.

[TonyOffermans]

Forgot to mention I am running Procon 1.5.3.2 and InnoDB 10.3.16

[Prophet731]

You might be hitting the limits for MySQL connections.

Try changing the max connections to something higher in the file /etc/mysql/my.cnf

max_connections = 300

 

[TonyOffermans]

Still crashes on a daily basis. I am trying to run my layer with procon.console.exe now, it gives much better response in my client. But still it decides to just give up on me every now and then. Resource consumption is fairly stable and low. It does produce these messages every few seconds though:

How to get rid of those messages? What is it that causes them? Are they just the commands sent by procon I can see in my console log? And is there any option to debug the crashes or better still, to try and prevent them? Thanks for your advice!

[Prophet731]

17 hours ago, TonyOffermans said:

Still crashes on a daily basis. I am trying to run my layer with procon.console.exe now, it gives much better response in my client. But still it decides to just give up on me every now and then. Resource consumption is fairly stable and low. It does produce these messages every few seconds though:

How to get rid of those messages? What is it that causes them? Are they just the commands sent by procon I can see in my console log? And is there any option to debug the crashes or better still, to try and prevent them? Thanks for your advice!

I don't know why it crashes, but I have seen those messages. I think it comes from a plugin but I don't know which one. Windows can monitor the procon service exe and restart it if it crashes.

[Hedius]

On 6/27/2020 at 1:25 PM, TonyOffermans said:

Still crashes on a daily basis. I am trying to run my layer with procon.console.exe now, it gives much better response in my client. But still it decides to just give up on me every now and then. Resource consumption is fairly stable and low. It does produce these messages every few seconds though:

How to get rid of those messages? What is it that causes them? Are they just the commands sent by procon I can see in my console log? And is there any option to debug the crashes or better still, to try and prevent them? Thanks for your advice!

Well, eh there should be a Debug.txt or dump (smth like that) in the main folder of PRoCon that contains the exception that caused the crash?

Yeah probably a plugin. Plugins can write to that interface if I remember correct.

[Timm]

Hi Tony, it will be difficult to solve the problem with crashes, because many of the plugin developers do not, but if you not have whatchdog for procon process, you can stat layer as service 

open CMD and

Sc create Procon01 binPath=D:\Procon\PRoCon.Service.exe DisplayName=Procon01

then go to Services and set 

 

Now, when layer crash, system will restart it automatically.