can anybody help me?
I have not been able to stop the stakign of kusama on the substrate for two months, it remains in a queue and never stops it (I have an enzyme connected to it)
I think it may be an enzyme problem, because the wifi icon appears as disconnected when I am inside the substrate
Related
I am trying to keep ESP8266 connected to my WiFi network forever.
Is this possible?
So far it is working only for some weeks and then disconnects from the router. How can I fix it? Maybe a reboot?
Could it be related to Lease Time or another setting in the router?
This can happen due to electronic failure, in other words, there may be overheating, poor contact of the components, a check in the project hardware and eliminate the possibility of a hardware error.
I recently bought an AWS IoT Button generation 2, and I'm trying to set it up.
I followed the steps in this tutorial: http://docs.aws.amazon.com/iot/latest/developerguide/iot-gs.html
I can connect to the wifi network generated by the button. I went to the .../index.html, attached my certs, etc.
Everything seemed fine, until I tried to use the button. When using the desktop-based instructions, I went to the MQTT Client and subscribed to it, but saw nothing when I clicked the button. When I tried to use the iOS app setup, I set the button action to send me a text message. I never got the text message. In both cases, the below occurred:
When I click the button, it blinks white for about a minute, then 3 short red blinks (meaning there was an error connecting to the wireless network).
I've tried these steps in my secure home network as well as the open network at my local library. Same results.
I've also tried starting over, repeating all steps from the tutorial and creating new certificates, etc. Same results.
Seems I'm not the only one having this problem.
Any help is much appreciated.
My button is now connected, although I have no idea why it wasn't working. I just followed the exact same steps I had been following on the same wifi network and everything, and all of a sudden it connected. Still looking for insight if anyone has some!
I have 4-7 sharepoint servers. We have a scom alert already implemented to generate alert if the server is down. But we want to implement scom alert if the website is down.
Can we genearate alert using scom by using ping functionality?
My idea is, we ping the server continuosly and when the website is unresponsive for some time we get alert saying that the website is unresposive.
Can this be implemented? And how much effort is needed? And do we need any other services to be implemented?
Any help would be appreciated.
Ravi,
Forgive me for the post being more philosophy and less answer.
For better or worse, Microsoft has resisted implemented a simple ping monitor in SCOM. Their is a solid reason for this. It would be overly leveraged by folks that don't know any better. The result of which would reflect poorly on the quality of SCOM as a monitoring tool. What I mean by that is that a ping monitor is a terrible idea as it doesn't tell the poor soul that was awoken at 2am much of anything beyond the highest level notion that something is wrong.
If you have 5 minutes to sit in front of the SCOM console to create a ping alert then you would serve your support teams much better if you spent those same 5 minutes creating a Web Application Availability monitor. The reason for this is that the Web App Avail monitor will actually look at the response to ensure that it is logical and successful.
Here is the documentation to create a Web Application Availability Monitor. It looks difficult only until your first implementation. It really is a snap. https://technet.microsoft.com/en-us/library/hh881882(v=sc.12).aspx
Consider that if you had a ping monitor and someone accidentally deleted your index.html file, your ping will happily chug along without telling anyone. Same with a bad code update. Heck, you could even stop your web application server and ping is still going to respond.
Conversely, If you had a Web App Avail monitor pointed at each of the nodes in a load balanced web farm and your load balancer failed, all of your Web monitors will continue to post as healthy while your monitor looking at the load balancer will start to fail. A quick glace at the console will tell your support team that indeed the issue is not with the web servers themselves.
It is a good philosophy to implement your monitors in a way that they testing the target as completely as possible and in the most isolated way possible. You would not want to point a Web App Avail monitor at a load balancer as you would not necessarily know which endpoint did not respond to SCOM to trigger the alert. Some folks go to great lengths to work around this by implementing health check pages that respond with there hostnames. This is usually not necessary, simply create a monitor against each individual node. You are going to want to monitor your load balancer directly so that you know it is up as well.
On another note, there already is a SharePoint management pack (actually one for each version of SharePoint) that you can download from MS for free. This management pack will automatically discovery and monitor all of the components of SharePoint in your infrastructure. It works quite well but if you are new to SCOM then the volume of data and alerts that it creates can be a bit overwhelming at first.
SharePoint 2016 (there is one for each version) management pack: https://blogs.technet.microsoft.com/wbaer/2015/09/08/system-center-operations-management-pack-for-sharepoint-server-2016-it-preview/
There is also a third party management pack that allows you to simply create ping monitors. People REALLY want this. I respectfully will tell you that that they are doing more harm then good in the majority of implementations that use this. But at the end of the day sometimes you just want something that works and you understand so here it is:
Ping management pack: https://www.opslogix.com/ping-management-pack/
When developing my web application using Django, I faced a problem, when I call some functions locally they work correctly, but once i call them over HTTP request they are not executed.
I asked around and i was told to execute them asynchronously outside the request response cycle using celery and a messaging queue server, it worked well, but still I don't understand why i have to execute some tasks asynchronously even when i don't have race condition and there's only one client calling the web service.
This is a big black spot for me because I make it work without really knowing how.
Can anyone explain it to me?
Thanks.
The two main benefits I know of for queue-based systems are:
One, a response can be given to the client without having to wait for work to be done. This lets pages load faster and clients spend less time waiting.
Second, a queue gives you a central location for scheduled jobs that multiple workers can draw from. If a certain component of your application can't keep up with the amount of work there is to do (or if it fails for some reason), you can have other instances of that component doing the work, and there is a single place where all of the work that needs to be done can be found.
I am currently working on a project involving a BlackWidow board that can establish a connection to the server, but cannot transmit data/receive acknowledgement or anything. For the moment we are trying to send a single byte. There are few examples, and most of them have the BlackWidow acting as a server. The examples where it it acting as a client will not work with us for whatever reason.
What could be the matter and are there some online resources that might help? Any help would be great!