Re: [Omuscd-general] No migration..

[g_remlin <g_r...@ro...>]

>
> I see that the process isn't on node which one node try to migrate
> (send?) to another.
> For example:
> I see that node 192.168.1.21 send signal migration process PID to node
> 192.168.1.22
> but on node 192.168.1.22 I didn't see this process.
>
> When I try to look where he (the process which try to migrate) is:
> (from node 192.168.1.21)
> cd /proc/PID/om/
> cat where
> the response is :
>
> 0.0.0.0 (instead 192.168.1.22)
>
>    
OK, because omuscd tries to migrate a process, it looks like it is 
working properly.
Confirm omuscd is trying to migrate the "correct" process, this is 
important, not all processes are migratable.
Check that the PID shown by omuscd matches one of the "timewaster" 
PID's, if it does, the problem is with the openMosix kernel itself, not 
omuscd.

You then need to look at /proc/$$/om/stay and /proc/$$/om/debug of the 
process that is supposed to migrate.
These will give you a clue what the openMosix kernel is doing. You may 
have to look at the openMosix source to see what they mean as I do not 
think they are documented (or post them to this list).