Timeline for How to tell (sub)kernels on a cluster not to try to access wolfram servers on startup?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 17, 2020 at 17:54 | answer | added | chris | timeline score: 8 | |
| Jan 16, 2020 at 15:00 | history | tweeted | twitter.com/StackMma/status/1217824029463261184 | ||
| Jan 16, 2020 at 13:53 | answer | added | chris | timeline score: 3 | |
| Jan 16, 2020 at 11:01 | history | edited | chris | CC BY-SA 4.0 |
added 218 characters in body
|
| Jan 16, 2020 at 10:52 | comment | added | Szabolcs | I do use clusters, but: 1. The nodes can access the internet 2. Subkernels do indeed take long to launch with occasional failures but I never managed to debug why :( Your finding is maybe a step towards understanding the reasons. | |
| Jan 16, 2020 at 10:50 | history | edited | chris | CC BY-SA 4.0 |
added 117 characters in body
|
| Jan 16, 2020 at 10:47 | comment | added | Szabolcs | This sounds like something that would be worth bringing up with Wolfram Support. It's not clear to me why subkernels should keep wanting to connect at all ... I did notice that sometimes subkernels print cloud-related messages on startup. | |
| Jan 16, 2020 at 10:46 | comment | added | Szabolcs | I could not originally understand the title. After reading the question, I edited the title in an attempt to make it clearer. Please review it. | |
| Jan 16, 2020 at 10:45 | history | edited | Szabolcs | CC BY-SA 4.0 |
added 8 characters in body; edited title
|
| Jan 16, 2020 at 10:37 | history | asked | chris | CC BY-SA 4.0 |