I was monitoring 30 urls in splunk through data inputs . Out of which 1 url showing 500 error rest of the urls are working fine . When asked to user they replied it is working fine and URL is also correct what do I need to do
Errors like that can be fleeting. Just because Splunk sees an error doesn't necessarily mean others will. Have your monitor report a problem only when an error repeats.
Related
In AWS Elemental MediaPackage, I am trying enable time-shifted viewing as below reference link:
https://docs.aws.amazon.com/mediapackage/latest/ug/time-shifted.html
But an HTTP error 404 occured. How can I fix it? Please help!
You can use Time-Shifted viewing on Elemental MediaPackage if start-over window is configured on your end-point. Looking at your description it looks like MediaPackage could not find a segment to satisfy your request. It may be due to one of the following :
Start Over window was configured after the end-point was created.
No ingest into the MediaPackage channel for the timestamps you requested.
Inorder to find out the reason behind this issue, I'll need the channel arn or the playback URL along with the timestamps when you made this request. Can you please provide these details to take a look ?
I am writing a ROS Node, and I am currently using ROS_INFO and ROS_ERROR for messages that are shown directly on the console. Now I want to switch to syslog and I want to use the syslog function for C.
That already works fine when I duplicate the log message and send it with syslog and ROS_INF/ERROR at the same time. But now I always have two line codes for the same error message in the code. Is there an easy way to show the syslog messages also on the console?!
Br Harald
Seems like rosconsole has multiple backends and you might be able to change that at compile time. Take a look at this thread
I'm setting up an iOS app to use the IP Messaging and video calling apis. I'm able to connect, create channels and setup a video call if I manually create hard-coded tokens for the app. However, if I want to use the PHP server (as described here https://www.twilio.com/docs/api/ip-messaging/guides/quickstart-ios) then I always get an error and it can't connect anymore.
I'm attaching a screenshot of what I see when I hit the http://localhost:8080 address which seems to produce a 500 Internal error on this URL: https://cds.twilio.com/v2/Streams
Thanks so much!
After much time spent on this I decided to try the node backend instead - under other server-side languages of the PHP and I have it running in 2 minutes! I used the exact same credentials as the ones that I was using on the PHP config file so either my PHP environment has something strange or the PHP backend needs some fixing. In any case, I'm able to move forward using the node backend, so if you run into the same issue just try node instead of PHP. woohoo!
I have a page where I am using swfobject and invoking the API's to control the youtube player.
When I run the application:
If the address is the local server (localhost) I can see all videos.
If I change the URL to my 192 internal address I get hit with the deadly restriction fail if these videos are marked as per the white and blacklists.
This seems like cheating but if I were to have a http server running on each client would this be illegal? If I could spin up an instance Cassini and now localhost solves the referrer issue.
Any thoughts?
Well, I run into the same problem and did some testing...
It seems, that Youtube restricts referers which consists of IP-Adresses.
For example, http://localhost/ works perfectly fine, no restrictions whatsoever, but with http://127.0.0.1/, bam, you're getting screwed.
Try putting
127.0.0.1 test.asd
into your hosts-file and surf to http://test.asd/. Should work fine.
So... what this means is, get yourself a domain (probably dyndns?) and everything should be fine.
I have a Node JS Server where I am using Socket.IO to stream content to the browser. It works great for about 45 minutes or so of streaming, then it will usually cut out. There are no "errors" reported in the terminal and the Node server acts like it is in, however the page I am serving clearly stops working.
What are my options for trying to get to the bottom of this? Could this be a configuration issue with Node/Socket.IO? is there any basic error logging you would recommend I setup?
Hard to say without seeing your code, but Socket.IO for NodeJS requires a heartbeat to maintain connection. It could be a bug in the client code for sending the heartbeat.