Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No buffer space available error in TaskMapper #36

Closed
salotz-sitx opened this issue Sep 15, 2021 · 2 comments
Closed

No buffer space available error in TaskMapper #36

salotz-sitx opened this issue Sep 15, 2021 · 2 comments

Comments

@salotz-sitx
Copy link
Collaborator

This error was found using the TaskMapper:

Traceback (most recent call last):
  File "/bgfs01/common/we_envs/envs/wepy_newnodes/lib/python3.7/site-packages/wepy/work_mapper/task_mapper.py", line 490, in run
    self._run_walker()
  File "/bgfs01/common/we_envs/envs/wepy_newnodes/lib/python3.7/site-packages/wepy/work_mapper/task_mapper.py", line 642, in _run_walker
    self._results_list[self.walker_idx] = ('Walker', serial_result)
  File "<string>", line 2, in __setitem__
  File "/bgfs01/common/we_envs/envs/wepy_newnodes/lib/python3.7/multiprocessing/managers.py", line 818, in _callmethod
    conn.send((self._id, methodname, args, kwds))
  File "/bgfs01/common/we_envs/envs/wepy_newnodes/lib/python3.7/multiprocessing/connection.py", line 206, in send
    self._send_bytes(_ForkingPickler.dumps(obj))
  File "/bgfs01/common/we_envs/envs/wepy_newnodes/lib/python3.7/multiprocessing/connection.py", line 398, in _send_bytes
    self._send(buf)
  File "/bgfs01/common/we_envs/envs/wepy_newnodes/lib/python3.7/multiprocessing/connection.py", line 368, in _send
    n = write(self._handle, buf)
OSError: [Errno 105] No buffer space available

Not sure how to approach this or if it is something we can even handle in wepy itself.

@alexrd
Copy link
Collaborator

alexrd commented Sep 15, 2021

@salotz-sitx
Copy link
Collaborator Author

Yep I was too hasty in this issue. Wanted to make sure I didn't forget about it :) I ended up looking at the log and it was just an out of memory error...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants