Exim not seding out mail, getting errors - exim

I dont know for how long, but just today I realized that exim is not sending out any mail. I tried restarting exim, nothing. Then i restarted the box, and still getting errors. I do not know why it is not sending. I cleared the mail queue, but that didnt do anything.. i dunno if that had anything to do with it but i tried it anyway. After clearing the mail queue i sent a message and went back to the mail queue and it cant be delivered, this is the error i get:
root#srv21:/etc/exim4# exim -qff
2012-07-31 14:56:32 1SvrdZ-0000gb-4h failed to expand condition "${perl{check_limits}}" for lookuphost router: Undefined subroutine &main::check_limits called.
2012-07-31 14:56:32 1Sw5eA-0004ZT-4p failed to expand condition "${perl{check_limits}}" for lookuphost router: Undefined subroutine &main::check_limits called.
2012-07-31 14:56:32 1Sw9t7-0006LJ-KF failed to expand condition "${perl{check_limits}}" for lookuphost router: Undefined subroutine &main::check_limits called.
2012-07-31 14:56:32 1Sw5eO-0004Zd-79 failed to expand condition "${perl{check_limits}}" for lookuphost router: Undefined subroutine &main::check_limits called.
2012-07-31 14:56:32 1SwApL-0006eu-Tv failed to expand condition "${perl{check_limits}}" for lookuphost router: Undefined subroutine &main::check_limits called.

this is evidently an error inside exim.conf. seems like you have to rewrite your perl conditions OR when installing exim you did not indicate that you would be using perl conditions (which is a prerequisite during make install)

Related

Angular7 + XHook gives ERROR TypeError: Illegal invocation

I have a chrome plugin runnin Xhook which intercepts xhr requests.
This used to work with angular js. Now I am using an Angular 7 application And I am getting an error when I make following request
this.http.get('someurl').subscribe((data: any) => {
});
Which triggers xhr.send(reqBody); in the angular http.js library. The error is on the subscribe part, if I remove this the error is gone.
The error is the following:
core.js:15724 ERROR TypeError: Illegal invocation
at ZoneTask.scheduleTask [as scheduleFn] (zone.js:3238)
at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.scheduleTask (zone.js:410)
at Object.onScheduleTask (zone.js:301)
at ZoneDelegate.push../node_modules/zone.js/dist/zone.js.ZoneDelegate.scheduleTask (zone.js:404)
at Zone.push../node_modules/zone.js/dist/zone.js.Zone.scheduleTask (zone.js:238)
at Zone.push../node_modules/zone.js/dist/zone.js.Zone.scheduleMacroTask (zone.js:261)
at scheduleMacroTaskWithCurrentZone (zone.js:1245)
at zone.js:3276
at _global.<computed>.proto.<computed> [as send] (zone.js:1569)
at Observable._subscribe (http.js:1726)
I am using this library: https://github.com/jpillora/xhook and the error is caused by line 478 facade.send = function(body) https://github.com/jpillora/xhook/blob/gh-pages/dist/xhook.js
I am thinking that: either angular tries to run the overridden function but something is not accessible because of zone.js, or I am missing certain properties, function in the object that overrides xhr?
If anyone has any information or solution on the subject that would be dearly appreciated.

Unhandled rejection Error: Chrome still being created

When I use { insertDefaultUI: false } to create a video I get an "Unhandled rejection Error: Chrome still being created" when trying to cleanup after I'm done with session.disconnect().
Any ideas...?
I'm on the TokBox dev team.
The error is not something you should be concerned with, it's something internal to the SDK.
The bug is that the error is appearing at all. I have created a bug report and this error should disappear in a future release. Until then you can safely ignore it.
Thanks for the report.
I'm having the very same problem when trying to unpublish my publisher
Could you guys provide a solution?
Unhandled rejection Error: Chrome still being created
at Object.chromeMixin.reset (https://static.opentok.com/v2/js/opentok.js:41755:16)
at reset (https://static.opentok.com/v2/js/opentok.js:42837:19)
at Publisher.destroy (https://static.opentok.com/v2/js/opentok.js:43211:7)
at defaultAction (https://static.opentok.com/v2/js/opentok.js:43524:20)
at executeDefaultAction (https://static.opentok.com/v2/js/opentok.js:25584:19)
at Object.api.dispatchEvent (https://static.opentok.com/v2/js/opentok.js:25735:7)
at Publisher.self.dispatchEvent (https://static.opentok.com/v2/js/opentok.js:25427:19)
at Object.streamDestroyed (https://static.opentok.com/v2/js/opentok.js:43527:16)
at Object.unpublishFromSession (https://static.opentok.com/v2/js/opentok.js:43507:16)
at Session.unpublish (https://static.opentok.com/v2/js/opentok.js:47031:19)
at Object.me.stop (https://x/rt.js:498:17)
at b.$scope.callBreak (https://x/ler.js:16:24)
at fn (eval at compile (https://ajax.googleapis.com/ajax/libs/angularjs/1.6.4/angular.min.js:239:266), <anonymous>:4:165)
From previous event:
at createChromeMixin (https://static.opentok.com/v2/js/opentok.js:41672:21)
at new Publisher (https://static.opentok.com/v2/js/opentok.js:42826:23)
at Object.initPublisher (https://static.opentok.com/v2/js/opentok.js:44275:21)
at Object.me.start (https://x/rt.js:457:27)
at b.$scope.start (https://x/ler.js:6:24)
at fn (eval at compile (https://ajax.googleapis.com/ajax/libs/angularjs/1.6.4/angular.min.js:239:266), <anonymous>:4:161)
at e (https://ajax.googleapis.com/ajax/libs/angularjs/1.6.4/angular.min.js:284:187)
at b.$eval (https://ajax.googleapis.com/ajax/libs/angularjs/1.6.4/angular.min.js:148:347)
at b.$apply (https://ajax.googleapis.com/ajax/libs/angularjs/1.6.4/angular.min.js:149:52)
at HTMLButtonElement.<anonymous> (https://ajax.googleapis.com/ajax/libs/angularjs/1.6.4/angular.min.js:284:239)
at HTMLButtonElement.dispatch (https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js:4:8549)
at HTMLButtonElement.r.handle (https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js:4:5252)
I might be a bit late, but I'll share my findings. When using a custom UI on your publisher, use the following event:
publisher.on('streamDestroyed',function(event){ event.preventDefault();});
This disallows opentok calling widget destroying events which causes the exception related to this question, however now I don't know how to stop the stream lol, since if I call event.target.destroy() will generate the same exception, lol ... so I'm trying to figure that out.

How do I hide or suppress react-native warning

I am getting the following warning in my react-native which I am told is something that I can ignore, but the actual warning is annoying.
The actual text of the error is the following...
Warning: Failed propType: Required prop sceneRendererProps.isRequired was not specified in SceneView. Check the render method of NavigationCard.
Is there a way I can get rid of, or suppress this error message specifically?
According to This Post
You should be able to do the following...
console.ignoredYellowBox = ['Warning: Failed propType: SceneView'];

Worklight 5.0.6 Documentation - Open Questions: "WL.FailResponse", "standard response object", "heartbeat in designated cases"

We are using WL 5.0.6.1 and we did not find all the information in the docs.
At
http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/topic/com.ibm.worklight.help.doc/apiref/r_wl_client_connect.html
does the onSuccess(??) receive any parameter/object as input? If so what type/JSON structure?
the onFailure receives a WL.FailResponse input object - is there any type/JSON-Structure definition available?
At:
http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/topic/com.ibm.worklight.help.doc/apiref/r_wl_client_invokeprocedure.html
it says: "the failure handler receives a standard response object." ... is there a type definition for a "standard response object"?
At:
http://pic.dhe.ibm.com/infocenter/wrklight/v5r0m6/topic/com.ibm.worklight.help.doc/apiref/r_wl_client_setheartbeatinterval.html
in the WorkingOffline PDF: http://public.dhe.ibm.com/software/mobile-solutions/worklight/docs/v600/05_04_Working_offline.pdf it says: " Both WL.Events.WORKLIGHT_IS_CONNECTED and
WL.Events.WORKLIGHT_IS_DISCONNECTED events can be fired
by heartbeat in designated cases"
What are these "designated cases"?
when the heartbeat fails to connect to the server for the first time (or every time) will the event WL.Events.WORKLIGHT_IS_DISCONNECTED be fired?
will the heartbeat continue to run/try once the WL.Events.WORKLIGHT_IS_DISCONNECTED was fired, or does it need to be reset/restarted manually?
if it does continue to run, will the event WL.Events.WORKLIGHT_IS_CONNECTED be fired once the heartbeat has it's first successful connection to the server again?
The object that comes in on the onSuccess can be any (JSON) object you return from the back-end wrapped in an invocationResult together with an isSuccessful and errors attributes:
An object that contains the data that is returned by the invoked procedure, and the invocation status. Its format is as follows:
**invocationResult = {
isSuccessful: Boolean,
errors : "Error Message"
// Procedure results go here
}**
Where:
isSuccessful – Contains true if the procedure invocation succeeded, false otherwise. If the invocation failed, the failure handler for the request is called.
errors – An optional array of strings containing error messages.
And for the failure:
The procedure was called but failed. In this case, the invocationResult property is added to the response received by the failure handler. This property has the same structure as the invocationResult property returned to the success handler, but the value of the isSuccessful attribute is false. For the structure of the invocationResult property, see invocationResult.

Some PHP errors/notices not displaying call stack information within Slim Framework

I'm using the Slim Framework.
Most PHP errors in my application output normal PHP error messages
Example code with an error that outputs the Call Stack:
echo 'missing semicolon at eol'
Error Output:
Parse error: syntax error, unexpected T_IF, expecting ',' or ';' in /data/www/app/routes/companies_routes.php on line 737
Call Stack:
0.0002 637144 1. {main}() /data/www/html/index.php:0
But other errors ( maybe just notices ) output a limited message that doesn't have a line number, file name, or call stack. This makes debugging these errors extremely time consuming.
Code with an error that outputs a limited error message
echo $an_undefined_variable;
Limited Message
Undefined variable: an_undefined_variable
I can't figure out what's going on. I've never had this problem before. I suspect it has something to do with the way Slim handles PHP errors. I've tried wrapping these errors in Try/Catch blocks, but that doesn't solve the problem.
The problem is that Slim is handling exceptions itself ( some sort of default behavior I've yet to track down ).
I've got my code wrapped in Try/Catch blocks, so when Slim catches a PHP error, it's throwing it's own Exception that I'm then outputting in my Catch block. If I remove my Catch block, Slim them outputs it's own complete error message that contains the stack as usual.
This surely means I'm not using Slim quite right, but that's a different question.