I am consuming data from the VM in the flow. So I have created a gateway to access the file inside VM. During scheduled run, the flow fails with the below error. During on-demand run, the flow succeeds.
I have even checked in the VM and the gateway is online. Any specific reason for this?
Related
Web API has GlobalConfiguration.Configuration.IncludeErrorDetailPolicy
= IncludeErrorDetailPolicy.Always; to turn on remote errors. (Allowing them to see them in a browser even if you are not browsing on the local machine.
But, near as I can tell, Service Fabric, running Web Api, does not support GlobalConfiguration.
Is there a way to configure things so I don't have to log into one of my Service Fabric server machines each time I want to see what a services error message is?
I recommend you don't show error details to everyone.
It's a security risk.
Consider moving your error logs out of your cluster. For instance, by using OMS, ELK or Application Insights.
We have started to explore Spring Cloud Consul and we see that if the Consul agent is down the app crashes when it started... is it the expected behavior? we have expected that the app will wait to the agent to be up and retry at least several times or at least that this behavior will be configurable...
Also if the agent was up at start it successfully registers the service in the catalog but if at some point the agent went down even for several seconds the app will fail to talk the agent and will not retry to talk with the agent again... This cause a scenario that the app is up but it is no longer talking to the agent again we would expect a retry...
It is an open issue that we are tracking.
I have MS Windows Server 2012 R2 running out of AWS facilities and want to watch its logs by CloudWatch.
Configuring Linux server, which is not an EC2 instance, works well as there are instructions how to install agents sending log records to CloudWatch regardless of where the server runs.
However, searching for such instructions for MS Windows server I am only able to find references for EC2Config Service, e.g. here http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/UsingConfig_WinAMI.html#UsingConfig_Install
It is possible, that I can simply install the service on "nonEC2" instance and it will work, but as the server is in production mode, I do not dare to do blind test ignoring risk of getting the server into problems.
Note, that I care about watching logs written to log files, I do not care (currently) about system log content.
It would help me if:
someone refers to positive experience with using EC2Config service on nonEC2 server
or someone proposes alternative method to get the log records into CloudWatch.
I have created a windows service.
When I install msi, this service goes to local services, but doesn't start. When i try to start it, it gives this error:
Windows could not start this service on Local computer.
Error 1053: The service didnot respond to the start or control request in a timely fashion.
One more thing is, that when I install msi as a service, it goes to local services, but doesn't start and gives warning that you don't have privileges to start this service.
Once you have created the service, go to "Services", and find the service you just created.
Right click on the service name, and select Properties. Under Log On, make sure the service is using an account that has permissions to the machine and anything your service needs. The default account is a Local System account, which has access to the following .
Microsoft has a couple of fixes to this problem here and here. They might help you.
I have a Windows service written using Topshelf. I'm trying to configure it to run using a Windows account with restricted privileges rather than using LocalSystem. That's also necessary as I'd like to connect to a database using integrated authentication.
The service works when run as LocalSystem (albeit with a database connection string containing credentials) and running the console application as my limited account (using runas) also works.
However, when I try to start the service the service control manager times out waiting for a response:
The service did not respond to the start or control request in a timely fashion.
I also get the following in the Application Popup event log:
Application Error : The exception unknown software exception (0xc06d007e) occurred in the application at location 0x77e4bef7.
The first thing that the application does is writes to a log file but it doesn't reach that when I start the service. The logging works if I run via the console.
Any suggestions what I might be missing or what I might try next?
This problem seems to be related to the server (a domain controller) rather than TopShelf. A service built with the .NET service component also exhibits the same behaviour.
The service runs successfully on a different machine (in the same domain).
Unfortunately this doesn't help diagnose the problem but gives me an acceptable workaround.
Check the MSDN article Debugging windows services which describes how you debug windows services.
I've just started seeing this on a few of my services written in .net 2.0. They'll start fine when the server boots, but if I were to restart them throughout the day, they would not start, and give this error message.
They currently ran under a domain account which has admin rights on the box, but for kicks, I switched it to Local System, and the service started normally. I stopped it, changed it back to the domain account (reentering the password), and it started normally again as expected.
Don't know if this counts as a 'fix' so much, but that's what worked for me.