Closed choksi81 closed 9 years ago
Please provide some details. Where does the nodemanager run? On Android? Then that's a known problem for which a fix exists (#1302 / r6994).
Replying to albert: Please provide some details. Where does the nodemanager run? On Android? Then that's a known problem for which a fix exists (#1302 / r6994). On Mac.
Please post your seattle/seattle_repy/v2/nodemanager.old and .new files (if available).
Replying to albert: Please post your seattle/seattle_repy/v2/nodemanager.old and .new files (if available). This is what I have $ pwd /Users/yyzh/seattle/seattle_repy/v2 $ ls -al total 24 drwxr-xr-x 4 yyzh staff 136 13 Feb 06:10 . drwxr-xr-x@ 230 yyzh staff 7820 13 Feb 06:11 .. -rw-r--r--@ 1 yyzh staff 6148 13 Feb 06:10 .DS_Store -rw-r--r-- 1 yyzh staff 899 12 Feb 19:20 example.1.2.r2py
Ah sorry, please look in the other v* directories for nodemanager logs too.
Replying to albert: Ah sorry, please look in the other v* directories for nodemanager logs too. $ pwd /Users/yyzh/seattle/seattle_repy/v3 dhcp-128-189-202-200:v3 yyzh$ ls cronlog.txt nodemanager.old softwareupdater.old
Could you post your results for ps -ef | grep nmmain? I'm curious to see how long the nodemanagers have been running for, which processes were responsible for starting the extra nodemanagers, and ideally, if the processes responsible are still running.
Replying to leonwlaw: Could you post your results for ps -ef | grep nmmain? I'm curious to see how long the nodemanagers have been running for, which processes were responsible for starting the extra nodemanagers, and ideally, if the processes responsible are still running. Attached.
Replying to yanyan: Replying to leonwlaw: Could you post your results for ps -ef | grep nmmain? I'm curious to see how long the nodemanagers have been running for, which processes were responsible for starting the extra nodemanagers, and ideally, if the processes responsible are still running.
Attached. nm.txt https://seattle.poly.edu/attachment/ticket/1316/nm.txt
Since there was no further report on a problem like this since it was originally reported, I'm closing this issue. The Betaseattleclearinghouse will get an update and start shipping a totally new installer pretty soon now, too. (This new installer has seen quite a bit of testing thanks to @SensibilityTestbed, and the problem didn't appear there.)
I created a customized install from beta Clearinghourse https://betaseattleclearinghouse.poly.edu/custom_install/ I split my local node into two. After install,