Tracert | Laravel package to log the users actions in the database | Database library

Here are some suggestions which should help.

You do not need to use CMD.EXE to launch TRACERT.EXE, as you can run it directly if it is on the path or fully qualify it's path. If you do use CMD then use "/C" flag to ensure it runs just that command.

Looks like a security group or a firewall issue. Run a traceroute to the destination IP from the machine with your browser.

If it stops at the last hop, it is most likely the security group not allowing connections to your port from the source subnet.

If the traceroute stops in the middle it is more likely a firewall issue.

I'm able to reproduce the second issue you report, i.e. the WPF process exiting when you try to send the signal to a console process. (The first issue, you've explained in your comment that it turned out to be a bug in your watch-dog code restarting the process even when it was signaled explicitly to exit.)

After investigation, it appears to me that this is caused by a race condition between the call to GenerateConsoleCtrlEvent() and the subsequent call to SetConsoleCtrlHandler(). It seems that if those calls occur too quickly, the Ctrl+C that is sent by GenerateConsoleCtrlEvent() remains visible to the default handling in the WPF app, causing the process to exit with the STATUS_CONTROL_C_EXIT code (i.e. the normal result from pressing Ctrl+C, but for the wrong process).

Interestingly, one of the things that stood out to me about the code you're using to send the signal, is that it restores the process state for the console and the signal handling in the same order those states were modified. This seems unusual to me, as one normally restores state in reverse order, to "back out" the state, as it were.

If one changes the code so that the signal handling is restored before freeing the attached console (i.e. the way one might normally write the code), then the problem with the host process receiving the signal and exiting reproduces the first time the method is called. I.e. it seems that the only reason it even works the first time is that there's some delay the first time that the host process calls the FreeConsole() function, that is sufficient to let the signal go unnoticed. The second time through, the delay no longer exists (possibly something got cached in the p/invoke layer…I didn't bother to investigate that part).

After that though, it works just like it would if you restored the state in the expected order.

Anyway…

I was able to reliably fix the issue by not restoring the current process's state until the target process had actually exited. In the proof-of-concept app I had to build in order to reproduce the issue, this was relatively simple, because I'd already implemented a TaskCompletionSource that is set when the Exited event is raised, and so I was able to pass the Task for that source to the StopProcess() method so it could await the Task before restoring the state.

I recommend you fix your code in a similar way. Note that you cannot call WaitForExit() on the Process itself, unless you do so from some thread other than the UI thread, because the Process class uses the UI thread to raise the Exited event, and so blocking the UI thread with a call to WaitForExit() will cause a deadlock. You could avoid that by putting the entire call to StopProcess() in a different thread, but that seems like overkill to me, especially when there's a more elegant way to implement the whole thing.

You can use any mechanism you like to wait for the process to terminate, as long as you take care to not deadlock the UI thread. But here's the code I wrote, in case you want to refer to it…

In the window class (note, completely broken for WPF as there's no MVVM here at all…this was just to get the basic minimal, complete example working):

If you have successfully configured your azure SQL to accept traffic from your IP then the issue seems to be with your local firewall blocking outbound connections

Things I would try:

• From Azure Portal connect to your database and try to use the query editor online to see if you are able to connect
• Use https://www.whatismyip.com/ to verify your public IP matches the one that's on the Azure SQL configuration (your error doesn't indicate that the server blocked the connection but worth double checking anyway)
• Lastly is to check from the local machine you are connecting that the "outbound" connection on port 1433 are not blocked. If you are connecting FROM an azure VM then you need to configure the NSG to allow outbound connection. If you are connecting from a local machine then you need to check if there's a local firewall or a VPN that's blocking this connection

From your description and the steps you described the last option above seems like the most likely scenario

You may have enabled proxy with gcloud, use-> gcloud config list to get the proxy settings

To unset proxy use: gcloud config unset proxy/[params] where params are address, port etc.

If you want to access the application on your Azure VM publicly with its public Ip address.

You could whitelist you client public IP in the NSG rule like, add the client public IP in the Source IP addresses.

Please note that

If you specify an address for an Azure resource, specify the private IP address assigned to the resource. Network security groups are processed after Azure translates a public IP address to a private IP address for inbound traffic, and before Azure translates a private IP address to a public IP address for outbound traffic.

Read https://docs.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview#security-rules

You seem to be using Bulk mode. Remember that Bulk mode is a mode to saturate RU when sending large number of operations. You mention you are sending < 10, so I would recommend (unless you have cases where you send a lot more) that you don't use Bulk mode in this case.

Please also check:

• Are you using a Singleton CosmosClient?
• Is the instance running in the same region as your write Cosmos DB region?
• Update your SDK, you are using version 3.6.0, there were improvements on Bulk (if you still want to use Bulk) in 3.11.0 to make it faster on low document count scenarios.

The tracert command returns an array of strings thus the Contains() function will not work here.

Here is a solution where I increase the $count variable which is initialized with 0 by 1 every time the tracert command contains the string Trace complete by using a regex. if the joined string doesn't contain the term, I increase the variable by 0.

Finally, the until condition will stop when the $count variable is greater equal 2.

The problem was preinstalled sshguard, which mistakenly added my IP to the list of blocked ones. There is a solution instruction in this answer.