\n\n\nAn error occurred while committing kernel: Failed to parse Redis response. Invalid Redis response payload: {\"Key\":\"timeout\",\"Result\":[\"\"]}
\n
Am I the only one getting the above error?
\n\nI started noticing a couple of days ago a strange behavior with the kernels. It commits successfully but later find out it did not run and sometimes there is no log at all. Then a Kernel I ran yesterday turned up with no log with version-1 showing the notebook cells visible but none of it had been run. Today I got the above error running a different kernel after an initial successfull commit.
\n\n@inversion and the Kaggle team, can you please look into this issue?
", "messages": [ { "id": "602781", "postDate": "08/19/2019 13:41:23", "content": "\n\n\nAn error occurred while committing kernel: Failed to parse Redis response. Invalid Redis response payload: {\"Key\":\"timeout\",\"Result\":[\"\"]}
\n
Am I the only one getting the above error?
\n\nI started noticing a couple of days ago a strange behavior with the kernels. It commits successfully but later find out it did not run and sometimes there is no log at all. Then a Kernel I ran yesterday turned up with no log with version-1 showing the notebook cells visible but none of it had been run. Today I got the above error running a different kernel after an initial successfull commit.
\n\n@inversion and the Kaggle team, can you please look into this issue?
", "rawMarkdown": "> An error occurred while committing kernel: Failed to parse Redis response. Invalid Redis response payload: {\"Key\":\"timeout\",\"Result\":[\"\"]}\n\nAm I the only one getting the above error?\n\nI started noticing a couple of days ago a strange behavior with the kernels. It commits successfully but later find out it did not run and sometimes there is no log at all. Then a Kernel I ran yesterday turned up with no log with version-1 showing the notebook cells visible but none of it had been run. Today I got the above error running a different kernel after an initial successfull commit.\n\n@inversion and the Kaggle team, can you please look into this issue?", "votes": null }, { "id": "602802", "postDate": "08/19/2019 14:05:01", "content": "No, you are not the only one to get that error. It was reported a few days ago and so far, it seems it is not totally fixed. I still have this issue also on a few kernels. It looks like creating a new kernel via copy/paste or fork may (sometimes) solve the problem and allow you to run your kernel ...
", "rawMarkdown": "No, you are not the only one to get that error. It was [reported a few days ago](https://www.kaggle.com/product-feedback/104351) and so far, it seems it is not totally fixed. I still have this issue also on a few kernels. It looks like creating a new kernel via copy/paste or fork may (sometimes) solve the problem and allow you to run your kernel ...", "votes": null }, { "id": "602834", "postDate": "08/19/2019 14:46:09", "content": "I'm not entirely sure if it's related, but I'm getting this too:\n> It commits successfully but later find out it did not run and sometimes there is no log at all. Then a Kernel I ran yesterday turned up with no log with version-1 showing the notebook cells visible but none of it had been run.
\n\nNo log at all, no cells run.\nIn my kernel I'm making small subset of features and pickling it. In Edit mode kernel crashes in the last cell: df.to_pickle(...). Though df is relatively small, ~700k lines x 15 columns. In my earlier kernels I succesfully pickled much larger dfs (~1000k+ x 200).
@fabiendaniel, I am actually getting this error with a forked kernel as well.
", "rawMarkdown": "fabiendaniel, I am actually getting this error with a forked kernel as well.", "votes": null }, { "id": "602847", "postDate": "08/19/2019 15:04:42", "content": "I guess that the issue is: the directory you try to write to either does not exist or is not writable...
", "rawMarkdown": "I guess that the issue is: the directory you try to write to either does not exist or is not writable...", "votes": null }, { "id": "602850", "postDate": "08/19/2019 15:07:38", "content": "@stanislavblinov, if it is not the case mentioned above by @cpmpml, it could just be the same issue as I reported manifesting in what you see.
", "rawMarkdown": "stanislavblinov, if it is not the case mentioned above by @cpmpml, it could just be the same issue as I reported manifesting in what you see.", "votes": null }, { "id": "602855", "postDate": "08/19/2019 15:15:10", "content": "yes, the results when forking kernels looks random ... it either solves the problem or not ...
", "rawMarkdown": "yes, the results when forking kernels looks random ... it either solves the problem or not ...", "votes": null }, { "id": "602860", "postDate": "08/19/2019 15:18:39", "content": "@cpmpml that was my 1st thought, but all operations with directories are unchanged since previous version which worked fine. Also, when I run df.to_pickle(...) cell in Edit mode, I can see in top right angle of kernel editor that disk space is filling up. Smth like 300Mb -> run cell -> 1.9Gb -> 2.9 Gb -> crash.\nSo I wrote here :) @sheriytm
I run into the sample problem / error with a very simple python notebook w/o any read/writes and no heavy lifting. Basically just some basic data viz in the ASHRAE competition.
\n\nError seem sporadic and independent of changes in the notebook.
", "rawMarkdown": "I run into the sample problem / error with a very simple python notebook w/o any read/writes and no heavy lifting. Basically just some basic data viz in the ASHRAE competition. \n\nError seem sporadic and independent of changes in the notebook.", "votes": null } ], "comments": [ { "id": 602802, "author_name": "fabiendaniel", "author_url": "", "post_date": "08/19/2019 14:05:01", "content": "No, you are not the only one to get that error. It was reported a few days ago and so far, it seems it is not totally fixed. I still have this issue also on a few kernels. It looks like creating a new kernel via copy/paste or fork may (sometimes) solve the problem and allow you to run your kernel ...
", "votes": null, "replies": [ { "id": 602842, "author_name": "sheriytm", "author_url": "", "post_date": "08/19/2019 14:59:31", "content": "@fabiendaniel, I am actually getting this error with a forked kernel as well.
", "votes": null, "replies": [] }, { "id": 602855, "author_name": "fabiendaniel", "author_url": "", "post_date": "08/19/2019 15:15:10", "content": "yes, the results when forking kernels looks random ... it either solves the problem or not ...
", "votes": null, "replies": [] } ] }, { "id": 602834, "author_name": "stanislavblinov", "author_url": "", "post_date": "08/19/2019 14:46:09", "content": "I'm not entirely sure if it's related, but I'm getting this too:\n> It commits successfully but later find out it did not run and sometimes there is no log at all. Then a Kernel I ran yesterday turned up with no log with version-1 showing the notebook cells visible but none of it had been run.
\n\nNo log at all, no cells run.\nIn my kernel I'm making small subset of features and pickling it. In Edit mode kernel crashes in the last cell: df.to_pickle(...). Though df is relatively small, ~700k lines x 15 columns. In my earlier kernels I succesfully pickled much larger dfs (~1000k+ x 200).
I guess that the issue is: the directory you try to write to either does not exist or is not writable...
", "votes": null, "replies": [] }, { "id": 602850, "author_name": "sheriytm", "author_url": "", "post_date": "08/19/2019 15:07:38", "content": "@stanislavblinov, if it is not the case mentioned above by @cpmpml, it could just be the same issue as I reported manifesting in what you see.
", "votes": null, "replies": [] }, { "id": 602860, "author_name": "stanislavblinov", "author_url": "", "post_date": "08/19/2019 15:18:39", "content": "@cpmpml that was my 1st thought, but all operations with directories are unchanged since previous version which worked fine. Also, when I run df.to_pickle(...) cell in Edit mode, I can see in top right angle of kernel editor that disk space is filling up. Smth like 300Mb -> run cell -> 1.9Gb -> 2.9 Gb -> crash.\nSo I wrote here :) @sheriytm
I run into the sample problem / error with a very simple python notebook w/o any read/writes and no heavy lifting. Basically just some basic data viz in the ASHRAE competition.
\n\nError seem sporadic and independent of changes in the notebook.
", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "602781": "> An error occurred while committing kernel: Failed to parse Redis response. Invalid Redis response payload: {\"Key\":\"timeout\",\"Result\":[\"\"]}\n\nAm I the only one getting the above error?\n\nI started noticing a couple of days ago a strange behavior with the kernels. It commits successfully but later find out it did not run and sometimes there is no log at all. Then a Kernel I ran yesterday turned up with no log with version-1 showing the notebook cells visible but none of it had been run. Today I got the above error running a different kernel after an initial successfull commit.\n\n@inversion and the Kaggle team, can you please look into this issue?", "602802": "No, you are not the only one to get that error. It was [reported a few days ago](https://www.kaggle.com/product-feedback/104351) and so far, it seems it is not totally fixed. I still have this issue also on a few kernels. It looks like creating a new kernel via copy/paste or fork may (sometimes) solve the problem and allow you to run your kernel ...", "602834": "I'm not entirely sure if it's related, but I'm getting this too:\n> It commits successfully but later find out it did not run and sometimes there is no log at all. Then a Kernel I ran yesterday turned up with no log with version-1 showing the notebook cells visible but none of it had been run.\n\nNo log at all, no cells run.\nIn my kernel I'm making small subset of features and pickling it. In Edit mode kernel crashes in the last cell: `df.to_pickle(...)`. Though df is relatively small, ~700k lines x 15 columns. In my earlier kernels I succesfully pickled much larger dfs (~1000k+ x 200).", "602842": "fabiendaniel, I am actually getting this error with a forked kernel as well.", "602847": "I guess that the issue is: the directory you try to write to either does not exist or is not writable...", "602850": "stanislavblinov, if it is not the case mentioned above by @cpmpml, it could just be the same issue as I reported manifesting in what you see.", "602855": "yes, the results when forking kernels looks random ... it either solves the problem or not ...", "602860": "cpmpml that was my 1st thought, but all operations with directories are unchanged since previous version which worked fine. Also, when I run `df.to_pickle(...)` cell in Edit mode, I can see in top right angle of kernel editor that disk space is filling up. Smth like 300Mb -> run cell -> 1.9Gb -> 2.9 Gb -> crash.\nSo I wrote here :) @sheriytm", "651168": "I run into the sample problem / error with a very simple python notebook w/o any read/writes and no heavy lifting. Basically just some basic data viz in the ASHRAE competition. \n\nError seem sporadic and independent of changes in the notebook." }, "source": "meta" }