I'm not sure your issues are ansible related, just triggered by ansible forks. I don't think upgrading to the lastest version will solve anything for you, you need to track down why your kernel is hitting those segfault issues.
On Fri, Aug 7, 2015 at 1:40 AM, <anandku...@greycampus.com> wrote: > How to upgrade to ansible latest version? and how to solve the the > following forks issue? Because i am very much struggling this issue? > ansible-playbook ssh.yml --force-handlers --forks=100 > > PLAY [Transfer and execute a script.] > ***************************************** > > TASK: [Transfer the script] > *************************************************** > changed: [dsrv493 -> 127.0.0.1] > changed: [dsrv487 -> 127.0.0.1] > changed: [dsrv486 -> 127.0.0.1] > changed: [dsrv209 -> 127.0.0.1] > changed: [dsrv488 -> 127.0.0.1] > changed: [dsrv531 -> 127.0.0.1] > Process SyncManager-1: > Traceback (most recent call last): > File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in > _bootstrap > self.run() > File "/usr/lib/python2.7/multiprocessing/process.py", line 114, in run > self._target(*self._args, **self._kwargs) > File "/usr/lib/python2.7/multiprocessing/managers.py", line 558, in > _run_server > server.serve_forever() > File "/usr/lib/python2.7/multiprocessing/managers.py", line 184, in > serve_forever > t.start() > File "/usr/lib/python2.7/threading.py", line 745, in start > _start_new_thread(self.__bootstrap, ()) > error: can't start new thread > Traceback (most recent call last): > File "/usr/lib/pymodules/python2.7/ansible/runner/__init__.py", line 85, in > _executor_hook > Process Process-85: > Traceback (most recent call last): > File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in > _bootstrap > Traceback (most recent call last): > File "/usr/bin/ansible-playbook", line 324, in <module> > self.run() > sys.exit(main(sys.argv[1:])) > File "/usr/bin/ansible-playbook", line 264, in main > File "/usr/lib/python2.7/multiprocessing/process.py", line 114, in run > self._target(*self._args, **self._kwargs) > File "/usr/lib/pymodules/python2.7/ansible/runner/__init__.py", line 81, in > _executor_hook > result_queue.put(return_data) > pb.run() > File "/usr/lib/pymodules/python2.7/ansible/playbook/__init__.py", line 348, > in run > File "<string>", line 2, in put > if not self._run_play(play): > File "/usr/lib/pymodules/python2.7/ansible/playbook/__init__.py", line 789, > in _run_play > File "/usr/lib/python2.7/multiprocessing/managers.py", line 758, in > _callmethod > if not self._run_task(play, task, False): > File "/usr/lib/pymodules/python2.7/ansible/playbook/__init__.py", line 497, > in _run_task > results = self._run_task_internal(task, include_failed=include_failed) > File "/usr/lib/pymodules/python2.7/ansible/playbook/__init__.py", line 439, > in _run_task_internal > results = runner.run() > File "/usr/lib/pymodules/python2.7/ansible/runner/__init__.py", line 1485, > in run > Process Process-86: > while not job_queue.empty(): > File "<string>", line 2, in empty > File "/usr/lib/python2.7/multiprocessing/managers.py", line 755, in > _callmethod > conn.send((self._id, methodname, args, kwds)) > results = self._parallel_exec(hosts) > File "/usr/lib/pymodules/python2.7/ansible/runner/__init__.py", line 1393, > in _parallel_exec > IOError: [Errno 32] Broken pipe > prc.start() > File "/usr/lib/python2.7/multiprocessing/process.py", line 130, in start > self._connect() > File "/usr/lib/python2.7/multiprocessing/managers.py", line 742, in > _connect > conn = self._Client(self._token.address, authkey=self._authkey) > File "/usr/lib/python2.7/multiprocessing/connection.py", line 175, in > Client > Traceback (most recent call last): > self._popen = Popen(self) > File "/usr/lib/python2.7/multiprocessing/forking.py", line 121, in __init__ > File "/usr/lib/python2.7/multiprocessing/process.py", line 258, in > _bootstrap > changed: [dsrv449 -> 127.0.0.1] > > Can you please tell how to solve this issue? Because this makes me lot of > issues while running in this 100 servers. > > > > On Friday, August 7, 2015 at 10:37:53 AM UTC+5:30, Brian Coca wrote: >> >> I don't know if this is a lack of memory, that normally gets a kernel >> message mentioning killing off processes, this looks like something >> much worse that is causing segfaults all over. >> >> >[2220566.328031] kernel BUG at >> > /build/buildd/linux-3.13.0/mm/memory.c:1838! >> >[2220566.328031] invalid opcode: 0000 [#3] SMP >> >> looks like some nasty kernel bug related to memory allocation. >> >> >> -- >> Brian Coca > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ansible-project+unsubscr...@googlegroups.com. > To post to this group, send email to ansible-project@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/85b11815-3a8e-451c-a532-5263938a090b%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- Brian Coca -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAJ5XC8nT0xLF4VDsqi%2BjA8v1vBr%3Dp0uzFLe6gMRnNDEBKpkaLQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
