Not sure where to put this post, but a big problem with 8.5.2 beta. Hard to explain, but we have a script that runs a MySQL command to verify replication is running correctly on a slave:

C:\Windows\system32\cmd.exe /c c:\mysql\bin\mysql.exe -u xxxxxxxxxxxxx --password=xxxxxxxxxxxxxxx -e "show slave status \G" | find "Slave_SQL_Running:"

For years, this has worked without a problem and takes about 2 seconds to complete, but when I installed 8.5.2 to address https://www.visualcron.c....aspx?g=posts&t=9521 , now the script sometimes takes up to 5 minutes, and not even sure what it is doing, but then fails about 25% of the time. Based on my testing, the command line is hanging as standard read and standard output error are both blank. I downgraded back to 8.5.1 and works normally again.

So I assume this is the execute Task you are using?

Can you attach screenshots of settings?

This Task - does it normally have large output? How large?

How long time is this Task running?

I know this is a tough one. In fact, now that I think about the fact that it does not fail until about 2 days after installation means it can't be a logon issue. I have no idea.

I'm still not being clear. The time is due to my script trying over and over again due to no output being captured. The actual command completes in less than a second. I am just using the time as an indicator of when it's not working. The issue is that my script can't capture the mysql.exe output for some reason.

You probably have more experience on this mysql.exe than we do. Can you do something similar that has zero dependencies so we can reproduce this here? I am thinking about altering the arguments or something like that.

I can try, but it won't be easy.

BTW, this is something we do frequently and I only for sure it's failing on this one job on this one machine, but if I can't capture output using these scripts, it will be a huge problem for us. I doubt it's limited to mysql.exe.

Installed and of course, works. Now, to wait 3 days. :)

3 days (really less than 3 days). Is the pace accelerating or is it "random"?

Disabled Auto Adjust, SFTP still fails:

Connection lost due to error 0

So the pattern holds. On 6/17, I downgraded to 8.5.1, worked. I upgraded to 8.5.2 that same day, worked. 3 days later, it stopped working again (same as the first time).

Looks like it stopped working right here:

[12:58:34] networkservice: Run Command: C:\Windows\system32\cmd.exe /c c:\mysql\bin\mysql.exe -u replication_monitor --password=xxxxxxxxxxxxx -e "show slave status \G" | find "Slave_IO_Running:"
[12:58:35] networkservice: Command line output StdoutRead: Slave_IO_Running: Yes
[12:58:35] networkservice: Line1: Slave_IO_Running: Yes
[12:58:35] networkservice: Line1: Slave_IO_Running: Yes
[12:58:35] networkservice: Slave_IO_Running = Yes
[12:58:35] networkservice: Check Slave_SQL_Running value
[12:58:35] networkservice: Run Command: C:\Windows\system32\cmd.exe /c c:\mysql\bin\mysql.exe -u replication_monitor --password=xxxxxxxxxxxxxxxxxx -e "show slave status \G" | find "Slave_SQL_Running:"
[12:58:36] networkservice: Command line output StdoutRead:
[12:58:36] networkservice: Line2:
[12:58:36] networkservice: Line2:

Now, why would it stop after 3 days?

Disabled Auto Adjust, SFTP still fails:

Connection lost due to error 0

Please use filezilla to connect with verbose logging on. Then send the log to support@visualcron.com along with screenshots of your VC settings.