I am using IPython 0.12 for a master-slave style HPC task. I just switch from 0.10.1 to 0.12. I do not change much about my code. But the ipcontroller and client program output the following message:
E: Unhandled error on recv: 11/Resource temporarily unavailable
E: Unhandled error on send: 11/Resource temporarily unavailable
E: Unhandled error on recv: 11/Resource temporarily unavailable
E: Unhandled error on send: 11/Resource temporarily unavailable
E: Unhandled error on recv: 11/Resource temporarily unavailable
E: Unhandled error on send: 11/Resource temporarily unavailable
The processes are still running. I even do not know where are the bugs? How can I trace the bugs? Is that just a warning?
This is a bug in libzmq-2.1.10, and should go away if you update to the current release (currently 2.1.11).
ref: http://lists.zeromq.org/pipermail/zeromq-dev/2011-October/013749.html
Related
I am trying to write my first electron app and deploy it to a system that requires me to run with the --no-sandbox option (I don't have root/sudo permissions on the system). While I am able to run with the --no-sandbox option, I see the following messages when I try to open a dialog to pick a file.
I can run vscode on the same system, and it also needs the --no-sandbox option, but I have not seen any of these messages while using vscode, so I assume it has something to do with the way may app is setup, or they way I am opening the dialog.
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Gtk-Message: 11:03:02.463: GtkDialog mapped without a transient parent. This is discouraged.
(my-first-electron:158778): dconf-WARNING **: 11:03:02.658: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”
(my-first-electron:158778): dconf-WARNING **: 11:03:02.705: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”
(my-first-electron:158778): dconf-WARNING **: 11:03:02.714: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”
Here is an example of how I am opening the dialog.
import { remote } from 'electron'
then later
buttonClicked = () => {
console.log(this)
ipcRenderer.send('do-something')
const dialog = remote.dialog
console.log(dialog.showOpenDialogSync(remote.getCurrentWindow(), {
properties: ['openFile']
}))
}
I am having a somewhat reproducible problem on a Swift server I'm running. This is a multi-threaded server, using Kitura. The basics are: After the server has been running for a period of time, download requests start needing retries from the client (usually three retries). The attempts from the client result in the server thread not terminating. On the server, the download problem shows up like this in the log:
[INFO] REQUEST /DownloadFile: ABOUT TO END ...
And then the request never terminates.
The relevant fragment code in my server looks like this:
// <snip>
Log.info(message: "REQUEST \(request.urlURL.path): ABOUT TO END ...")
do {
try self.response.end()
Log.info(message: "REQUEST \(request.urlURL.path): STATUS CODE: \(response.statusCode)")
} catch (let error) {
Log.error(message: "Failed on `end` in failWithError: \(error.localizedDescription); HTTP status code: \(response.statusCode)")
}
Log.info(message: "REQUEST \(request.urlURL.path): COMPLETED")
// <snip>
That is, the server clearly seems to hang on the call to end (a Kitura method). See also https://github.com/crspybits/SyncServerII/blob/master/Sources/Server/Setup/RequestHandler.swift#L105
Immediately before this issue came up last time, I observed the following in my server log:
[2017-07-12T15:31:23.302Z] [ERROR] [HTTPServer.swift:194 listen(listenSocket:socketManager:)] Error accepting client connection: Error code: 5(0x5), ERROR: SSL_accept, code: 5, reason: DH lib
[2017-07-12T15:31:23.604Z] [ERROR] [HTTPServer.swift:194 listen(listenSocket:socketManager:)] Error accepting client connection: Error code: 1(0x1), ERROR: SSL_accept, code: 1, reason: Could not determine error reason.
[2017-07-12T15:31:23.995Z] [ERROR] [HTTPServer.swift:194 listen(listenSocket:socketManager:)] Error accepting client connection: Error code: 1(0x1), ERROR: SSL_accept, code: 1, reason: Could not determine error reason.
[2017-07-12T15:40:32.941Z] [ERROR] [HTTPServer.swift:194 listen(listenSocket:socketManager:)] Error accepting client connection: Error code: 1(0x1), ERROR: SSL_accept, code: 1, reason: Could not determine error reason.
[2017-07-12T15:42:43.000Z] [VERBOSE] [HTTPServerRequest.swift:215 parsingCompleted()] HTTP request from=139.162.78.135; proto=https;
[INFO] REQUEST RECEIVED: /
[2017-07-12T16:32:38.479Z] [ERROR] [HTTPServer.swift:194 listen(listenSocket:socketManager:)] Error accepting client connection: Error code: 1(0x1), ERROR: SSL_accept, code: 1, reason: Could not determine error reason.
I am not sure where this is coming from in the sense that I'm not sure if one of my client's is generating this. I do not explicitly make requests to my server with "/". (I do occasionally see requests made to my server from clients that are not mine-- it is possible this is one of these). Note that all except one of these log messages are coming from Kitura, not directly from my code. My log message is [INFO] REQUEST RECEIVED: /.
If I was a betting man, I'd say the above errors put my server into a state where afterwards, I see this download/retry behavior.
My only solution at this point is to restart the server. From which point the issue doesn't immediately happen.
Thoughts?
I'm not sure if this addresses the root problem, or if it's just a work-around, but it appears to be working. With the server as stated in the question, I had been using Kitura's built-in SSL support. I have now switched to using NGINX as a front-end, and no longer use Kitura's built-in SSL support. NGINX takes care of all the HTTPS/SSL details. Since doing this (about a month ago), and with the server running for all of that intervening time, I have not experience the not terminating issue reported in this question. See also https://github.com/crspybits/SyncServerII/issues/28
From my react native application, I am trying to authenticate against FB. Instead of directly using fbsdk, I was planning to use a wrapper around it.
I tried two wrappers.
https://github.com/xxsnakerxx/react-native-social-auth
https://github.com/magus/react-native-facebook-login
In both cases, I end up with a WebView which won't callback the app.
I have raised two issues
https://github.com/magus/react-native-facebook-login/issues/187
https://github.com/xxsnakerxx/react-native-social-auth/issues/6
XCode logs has below entries which I am not able to decipher
2016-12-09 06:13:29.757 XXXX[61829:8555589] -canOpenURL: failed for URL: "fbauth2:/" - error: "The operation couldn’t be completed. (OSStatus error -10814.)"
2016-12-09 06:13:29.759 XXXX[61829:8555589] -canOpenURL: failed for URL: "fbauth2:/" - error: "The operation couldn’t be completed. (OSStatus error -10814.)"
and..
__nw_socket_service_writes_block_invoke sendmsg(fd 9, 31 bytes): socket has been closed
2016-12-09 06:13:36.670958 XXXX[61829:8574160] [] nw_endpoint_flow_protocol_error [15.1 157.240.7.20:443 cancelled socket-flow (null)] Socket protocol sent error: [32] Broken pipe
2016-12-09 06:13:36.671154 XXXX[61829:8574160] [] nw_endpoint_flow_protocol_disconnected [15.1 157.240.7.20:443 cancelled socket-flow (null)] Output protocol disconnected
And the WebView post all the authentication looks like
Eventually successful with react-native-social-auth. Missed a few configurations.
I get the following error when trying to debug a local java application in eclipse.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: connect failed: Connection refused
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
I read that it might be caused by something using the same port as the one eclipse wants to use for debugging, but how do I determine the port number. I couldn't find anything in the error log or the preferences.
Any ideas?
I ran into the same issue and it turns out I was specifying server=n parameter in the jdwp debug string. It turns out that if we specify server=n in the debug connection string, it'll attempt to attach/connect to that port instead of listening on it. Switching to server=y solved my issue. It's documented in the
official jpda documentation.
Maybe it's your antivirus. Are you using avast if so look at this https://feedback.avast.com/responses/eclipse-debug-functionality-not-working-after-upgrade-to-avast-2014
The solution is upgrading to the latest version of avast (http://forum.avast.com/index.php?topic=139606.0)
Please ensure that, the below entry is there in /etc/hosts file (for mac/linux)
127.0.0.1 localhost
Previously I unknowingly commented out this line, so it worked for me after reverting back. Hope this helps.
I use the Zend libray, especially Loader class. But I take the following exception:
Uncaught exception 'Zend_Http_Client_Adapter_Exception' with message 'Unable to Connect to ssl://www.googleapis.com:443. Error #0:
I should say that when I run my code local, I don't face any problem, but the exception show when I try to run my file in server. The server I use has ssl security. Is there any possibility to there is any conflict with it?
This error may be caused by SSL level error like untrusted/expired SSL certificate which can be caused by wrong local system date.
If you on Ubuntu try add in your php.ini
openssl.capath=/etc/ssl/certs
For more info read this issue