Marionnet - A virtual network laboratory

Error "a process died unexpectedly" when starting project

Asked by kern on 2012-04-27

Hello!

I recently installed marionnet via the marionnet-from-scratch script.

My first test-project has been as simple as possible, connectoing two machines via a hub. Meanwhile I also tryed some other topologies, but I always get the same error when starting the project:

"A process died unexpectedly"
"The process linux-2.6.18-ghost with pid xxxxx allowing the simulation of cumputer m1 died unexpectedly ..."

I can't really figure what's causing the problem. Here is the output of the debug log:

<--snip-->
[8]: Starting up the device m1...
[32]: process#spawn: the command line for wirefilter is:
---
  wirefilter -l LR0.000000 -D LR0.000000 --noise LR0 -d
  LR0.000000+0.000000 -l RL0.000000 -D RL0.000000 --noise RL0
  -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hublet-1-socket-575933723:/tmp/marionnet-578881064.dir/hublet-0-socket-160322301
---
[32]: spawning process: a process (wirefilter) was just spawned (pid 28258).
172.23.0.2 being added to access control list
[31]: Executing: dd if=/dev/zero bs=1024 seek=1048576 count=1 of=/tmp/marionnet-578881064.dir/sparse-swap-510365912
1+0 records in
1+0 records out
1024 bytes (1.0 kB) copied, 2.0136e-05 s, 50.9 MB/s
[31]: Created the swap file /tmp/marionnet-578881064.dir/sparse-swap-510365912.
[31]: Executing: export PATH=$PATH:/sbin:/usr/sbin:/usr/local/sbin; mkswap /tmp/marionnet-578881064.dir/sparse-swap-510365912
Setting up swapspace version 1, size = 1048572 KiB
no label, UUID=ad3118b3-f0a2-4169-8ba0-22c89f9017d2
[31]: Executed mkswap on the swap file /tmp/marionnet-578881064.dir/sparse-swap-510365912.
[31]: process#spawn: the command line for linux-2.6.18-ghost is:
---
  /usr/local/share/marionnet/kernels/linux-2.6.18-ghost
  keyboard_layout=us
  eth0=daemon,02:04:06:3c:08:f1,unix,/tmp/marionnet-578881064.dir/hublet-1-socket-575933723/ctl
  ubd0s=/tmp/marionnet-578881064.dir/test1/states/28028-30707-22340.cow,/usr/local/share/marionnet/filesystems/machine-debian-lenny-sid-2008
  ubdb=/tmp/marionnet-578881064.dir/sparse-swap-510365912
  umid=m1 mem=48M root=98:0
  hostfs=/tmp/marionnet-578881064.dir/test1/hostfs/2
  hostname=m1 xterm=xterm,-T,-e
  eth42=tuntap,wrong-tap-name,42:42:8b:cb:4a:e4,172.23.0.254
  con0=none con1=none con2=none con3=none con4=none con5=none
  con6=none ssl0=xterm ssl1=none ssl2=none ssl3=none ssl4=none
  ssl5=none ssl6=none console=ttyS0
---
[31]: spawning process: a process (linux-2.6.18-ghost) was just spawned (pid 28265).
[8]: The device m1 was started up
[8]: A progress bar dialog window was destroyed.
[8]: A progress bar dialog window was destroyed.
[8]: task_runner: The task "Startup m1" succeeded.
[8]: task_runner: I'm ready for the next task...
[8]: task_runner: Executing the task "Startup m2"
[8]: Starting up the device m2...
[8]: (creating processes for m2 first...)
[8]: About to create the simulated device m2: it's connected to 1 cables.
[8]: Relevant states for m2 are 1
[8]: Making a copy of a cow file: the command line is: if [ -e /tmp/marionnet-578881064.dir/test1/states/18917-45578-28694.cow ]; then cp --sparse=always /tmp/marionnet-578881064.dir/test1/states/18917-45578-28694.cow /tmp/marionnet-578881064.dir/test1/states/41894-60427-35472.cow; else true; fi
[8]: About to start the machine m2
  with filesystem: /usr/local/share/marionnet/filesystems/machine-debian-lenny-sid-2008
  cow file: /tmp/marionnet-578881064.dir/test1/states/41894-60427-35472.cow
  kernel: /usr/local/share/marionnet/kernels/linux-2.6.18-ghost
  xnest: false
[8]: Socket name "/tmp/marionnet-578881064.dir/hublet-0-socket-684474850" reserved for vde_switch.
[8]: Socket name "/tmp/marionnet-578881064.dir/hublet-1-socket-781314895" reserved for vde_switch.
[8]: Spawning the process which will create the socket /tmp/marionnet-578881064.dir/hublet-0-socket-684474850
[8]: process#spawn: the command line for vde_switch is:
---
  vde_switch -x -n 3 -mod 777 -unix
  /tmp/marionnet-578881064.dir/hublet-0-socket-684474850
---
[8]: spawning process: a process (vde_switch) was just spawned (pid 28269).
Binary file /proc/net/unix matches
[8]: Ok, the socket now exists. Spawning succeeded.
[8]: Spawning the process which will create the socket /tmp/marionnet-578881064.dir/hublet-1-socket-781314895
[8]: process#spawn: the command line for vde_switch is:
---
  vde_switch -x -n 3 -mod 777 -unix
  /tmp/marionnet-578881064.dir/hublet-1-socket-781314895
---
[8]: spawning process: a process (vde_switch) was just spawned (pid 28272).
Binary file /proc/net/unix matches
[8]: Ok, the socket now exists. Spawning succeeded.
[8]: eth42 has IP 172.23.0.3
[8]: Working on cable d2 (direct) [H1,port2] -> [m2,eth0]
[8]: Increment_alive_endpoint_no
[8]: The reference count is now 2
[8]: The reference count is now 3
[8]: The reference count raised to three: starting up a cable
[8]: Starting up the device d2...
[8]: (creating processes for d2 first...)
[8]: About to create the simulated device d2: it's connected to 0 cables.
[8]: Left hublet process socket name is "/tmp/marionnet-578881064.dir/hublet-1-socket-332149307"
[8]: Right hublet process socket name is "/tmp/marionnet-578881064.dir/hublet-0-socket-684474850"
[8]: (processes for d2 were created...)
[8]: Starting up the device d2...
[8]: process#spawn: the command line for wirefilter is:
---
  wirefilter --blink
  /tmp/.marionnet-blinker-server-socket-958286523 --blinkid
  ((id: 1; port: 1)(id: -1; port: -1)) -l LR0.000000 -D
  LR0.000000 --noise LR0 -d LR0.000000+0.000000 -l RL0.000000
  -D RL0.000000 --noise RL0 -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hublet-1-socket-332149307:/tmp/marionnet-578881064.dir/hublet-0-socket-684474850
---
[8]: spawning process: a process (wirefilter) was just spawned (pid 28280).
[8]: The device d2 was started up
[8]: (processes for m2 were created...)
[8]: Starting up the device m2...
[41]: process#spawn: the command line for wirefilter is:
---
  wirefilter -l LR0.000000 -D LR0.000000 --noise LR0 -d
  LR0.000000+0.000000 -l RL0.000000 -D RL0.000000 --noise RL0
  -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hublet-1-socket-781314895:/tmp/marionnet-578881064.dir/hublet-0-socket-684474850
---
[41]: spawning process: a process (wirefilter) was just spawned (pid 28286).
172.23.0.3 being added to access control list
[40]: Executing: dd if=/dev/zero bs=1024 seek=1048576 count=1 of=/tmp/marionnet-578881064.dir/sparse-swap-460255646
1+0 records in
1+0 records out
1024 bytes (1.0 kB) copied, 2.3941e-05 s, 42.8 MB/s
[40]: Created the swap file /tmp/marionnet-578881064.dir/sparse-swap-460255646.
[40]: Executing: export PATH=$PATH:/sbin:/usr/sbin:/usr/local/sbin; mkswap /tmp/marionnet-578881064.dir/sparse-swap-460255646
Setting up swapspace version 1, size = 1048572 KiB
no label, UUID=d722685b-251c-4965-a2ae-f84639668ece
[40]: Executed mkswap on the swap file /tmp/marionnet-578881064.dir/sparse-swap-460255646.
[40]: process#spawn: the command line for linux-2.6.18-ghost is:
---
  /usr/local/share/marionnet/kernels/linux-2.6.18-ghost
  keyboard_layout=us
  eth0=daemon,02:04:06:89:63:89,unix,/tmp/marionnet-578881064.dir/hublet-1-socket-781314895/ctl
  ubd0s=/tmp/marionnet-578881064.dir/test1/states/41894-60427-35472.cow,/usr/local/share/marionnet/filesystems/machine-debian-lenny-sid-2008
  ubdb=/tmp/marionnet-578881064.dir/sparse-swap-460255646
  umid=m2 mem=48M root=98:0
  hostfs=/tmp/marionnet-578881064.dir/test1/hostfs/3
  hostname=m2 xterm=xterm,-T,-e
  eth42=tuntap,wrong-tap-name,42:42:fe:64:23:34,172.23.0.254
  con0=none con1=none con2=none con3=none con4=none con5=none
  con6=none ssl0=xterm ssl1=none ssl2=none ssl3=none ssl4=none
  ssl5=none ssl6=none console=ttyS0
---
[40]: spawning process: a process (linux-2.6.18-ghost) was just spawned (pid 28293).
[8]: The device m2 was started up
[8]: A progress bar dialog window was destroyed.
[8]: A progress bar dialog window was destroyed.
[8]: task_runner: The task "Startup m2" succeeded.
[8]: task_runner: I'm ready for the next task...
[6]: You don't deadlock here m2, do you? -1
[6]: You don't deadlock here m2, do you? 0
[6]: About to destroy the simulated device m2
[6]: (destroying the on/sleeping device m2. Powering it off first...)
[6]: Powering off the device m2...
[6]: ** Terminating the internal cable processes of m2...
[46]: simulated_network: stop_monitoring the process wirefilter (pid 28286): BEGIN
[46]: simulated_network: stop_monitoring the process wirefilter (pid 28286): SUCCESS
[46]: About to terminate the process with pid 28286...
[46]: SUCCESS: terminating the process with pid 28286 succeeded.
172.23.0.3 being removed from access control list
[45]: Executing: rm -f /tmp/marionnet-578881064.dir/sparse-swap-460255646
[45]: Deleted the swap file /tmp/marionnet-578881064.dir/sparse-swap-460255646.
[45]: simulated_network: stop_monitoring the process /usr/local/share/marionnet/kernels/linux-2.6.18-ghost (pid 28293): BEGIN
[45]: simulated_network: stop_monitoring the process /usr/local/share/marionnet/kernels/linux-2.6.18-ghost (pid 28293): SUCCESS
/bin/sh: uml_mconsole: command not found
[46]: simulated_network: waitpid 28286 failed. (9)
[6]: About to destroy the simulated device m2
[6]: (destroying the off device m2: decrementing its cables rc...)
[6]: Unpinning the cable d2 (direct) [H1,port2] -> [m2,eth0] [6]: Decrement_alive_endpoint_no
[6]: The reference count is now 3
[6]: The reference count is now 2
[6]: The reference count dropped below three: destroying a cable
[6]: About to destroy the simulated device d2
[6]: (destroying the on/sleeping device d2. Powering it off first...)
[6]: Powering off the device d2...
[6]: simulated_network: stop_monitoring the process wirefilter (pid 28280): BEGIN
[6]: simulated_network: stop_monitoring the process wirefilter (pid 28280): SUCCESS
[6]: About to terminate the process with pid 28280...
[6]: SUCCESS: terminating the process with pid 28280 succeeded.
[6]: simulated_network: waitpid 28280 failed. (9)
[6]: About to destroy the simulated device d2
[6]: (destroying the off device d2: decrementing its cables rc...)
[6]: (destroying the simulated device implementing d2...)
[6]: The method destroy has been called on the device d2: begin
[6]: Resuming d2 before destruction (it might be needed)...
[6]: Shutting down d2 before destruction...
[6]: Now terminate d2's hublets...
[6]: Ok, the hublets of d2 were destroyed...
[6]: The method destroy has been called on the device d2: end
[6]: We're not deadlocked yet (d2). Great.
[6]: The simulated device d2 was destroyed with success
[6]: The simulated device d2 was destroyed with success
[6]: The cable d2 (direct) [H1,port2] -> [m2,eth0] was unpinned with success
[6]: (destroying the simulated device implementing m2...)
[6]: The method destroy has been called on the device m2: begin
[6]: Resuming m2 before destruction (it might be needed)...
[6]: Shutting down m2 before destruction...
[6]: Now terminate m2's hublets...
[6]: Terminating a device hublet process (pid 28269) of m2...
[6]: simulated_network: stop_monitoring the process vde_switch (pid 28269): BEGIN
[6]: simulated_network: stop_monitoring the process vde_switch (pid 28269): SUCCESS
[6]: About to terminate the process with pid 28269...
[6]: SUCCESS: terminating the process with pid 28269 succeeded.
[6]: simulated_network: waitpid 28269 failed. (9)
[6]: Raising exception Simulation_level.ProcessIsntInTheRightState("kill_with_signal") at File "simulation_level.ml", line 149, characters 16-69
[6]: ...ok, a hublet process (pid 28269) of m2 was terminated
[6]: Terminating a device hublet process (pid 28272) of m2...
[6]: simulated_network: stop_monitoring the process vde_switch (pid 28272): BEGIN
[6]: simulated_network: stop_monitoring the process vde_switch (pid 28272): SUCCESS
[6]: About to terminate the process with pid 28272...
[6]: SUCCESS: terminating the process with pid 28272 succeeded.
[6]: simulated_network: waitpid 28272 failed. (9)
[6]: Raising exception Simulation_level.ProcessIsntInTheRightState("kill_with_signal") at File "simulation_level.ml", line 149, characters 16-69
[6]: ...ok, a hublet process (pid 28272) of m2 was terminated
[6]: Ok, the hublets of m2 were destroyed...
[6]: The method destroy has been called on the device m2: end
[6]: We're not deadlocked yet (m2). Great.
[6]: The simulated device m2 was destroyed with success
[6]: About to destroy the simulated device m2
[6]: (destroying the already 'no-device' device m2. Doing nothing...)
[6]: The simulated device m2 was destroyed with success
[6]: The simulated device m2 was destroyed with success
[6]: You don't deadlock here m1, do you? -1
[6]: You don't deadlock here m1, do you? 0
[6]: About to destroy the simulated device m1
[6]: (destroying the on/sleeping device m1. Powering it off first...)
[6]: Powering off the device m1...
[6]: ** Terminating the internal cable processes of m1...
[48]: simulated_network: stop_monitoring the process wirefilter (pid 28258): BEGIN
[48]: simulated_network: stop_monitoring the process wirefilter (pid 28258): SUCCESS
[48]: About to terminate the process with pid 28258...
[48]: SUCCESS: terminating the process with pid 28258 succeeded.
172.23.0.2 being removed from access control list
[47]: Executing: rm -f /tmp/marionnet-578881064.dir/sparse-swap-510365912
[47]: Deleted the swap file /tmp/marionnet-578881064.dir/sparse-swap-510365912.
[47]: simulated_network: stop_monitoring the process /usr/local/share/marionnet/kernels/linux-2.6.18-ghost (pid 28265): BEGIN
[47]: simulated_network: stop_monitoring the process /usr/local/share/marionnet/kernels/linux-2.6.18-ghost (pid 28265): SUCCESS
/bin/sh: uml_mconsole: command not found
[48]: simulated_network: waitpid 28258 failed. (9)
[6]: About to destroy the simulated device m1
[6]: (destroying the off device m1: decrementing its cables rc...)
[6]: Unpinning the cable d1 (direct) [H1,port1] -> [m1,eth0] [6]: Decrement_alive_endpoint_no
[6]: The reference count is now 3
[6]: The reference count is now 2
[6]: The reference count dropped below three: destroying a cable
[6]: About to destroy the simulated device d1
[6]: (destroying the on/sleeping device d1. Powering it off first...)
[6]: Powering off the device d1...
[6]: simulated_network: stop_monitoring the process wirefilter (pid 28252): BEGIN
[6]: simulated_network: stop_monitoring the process wirefilter (pid 28252): SUCCESS
[6]: About to terminate the process with pid 28252...
[6]: SUCCESS: terminating the process with pid 28252 succeeded.
[6]: simulated_network: waitpid 28252 failed. (9)
[6]: About to destroy the simulated device d1
[6]: (destroying the off device d1: decrementing its cables rc...)
[6]: (destroying the simulated device implementing d1...)
[6]: The method destroy has been called on the device d1: begin
[6]: Resuming d1 before destruction (it might be needed)...
[6]: Shutting down d1 before destruction...
[6]: Now terminate d1's hublets...
[6]: Ok, the hublets of d1 were destroyed...
[6]: The method destroy has been called on the device d1: end
[6]: We're not deadlocked yet (d1). Great.
[6]: The simulated device d1 was destroyed with success
[6]: The simulated device d1 was destroyed with success
[6]: The cable d1 (direct) [H1,port1] -> [m1,eth0] was unpinned with success
[6]: (destroying the simulated device implementing m1...)
[6]: The method destroy has been called on the device m1: begin
[6]: Resuming m1 before destruction (it might be needed)...
[6]: Shutting down m1 before destruction...
[6]: Now terminate m1's hublets...
[6]: Terminating a device hublet process (pid 28240) of m1...
[6]: simulated_network: stop_monitoring the process vde_switch (pid 28240): BEGIN
[6]: simulated_network: stop_monitoring the process vde_switch (pid 28240): SUCCESS
[6]: About to terminate the process with pid 28240...
[6]: SUCCESS: terminating the process with pid 28240 succeeded.
[6]: simulated_network: waitpid 28240 failed. (9)
[6]: Raising exception Simulation_level.ProcessIsntInTheRightState("kill_with_signal") at File "simulation_level.ml", line 149, characters 16-69
[6]: ...ok, a hublet process (pid 28240) of m1 was terminated
[6]: Terminating a device hublet process (pid 28244) of m1...
[6]: simulated_network: stop_monitoring the process vde_switch (pid 28244): BEGIN
[6]: simulated_network: stop_monitoring the process vde_switch (pid 28244): SUCCESS
[6]: About to terminate the process with pid 28244...
[6]: SUCCESS: terminating the process with pid 28244 succeeded.
[6]: simulated_network: waitpid 28244 failed. (9)
[6]: Raising exception Simulation_level.ProcessIsntInTheRightState("kill_with_signal") at File "simulation_level.ml", line 149, characters 16-69
[6]: ...ok, a hublet process (pid 28244) of m1 was terminated
[6]: Ok, the hublets of m1 were destroyed...
[6]: The method destroy has been called on the device m1: end
[6]: We're not deadlocked yet (m1). Great.
[6]: The simulated device m1 was destroyed with success
[6]: About to destroy the simulated device m1
[6]: (destroying the already 'no-device' device m1. Doing nothing...)
[6]: The simulated device m1 was destroyed with success
[6]: The simulated device m1 was destroyed with success
[20]: *** Rebooting the wirefilter with pid 28226
[20]: simulated_network: stop_monitoring the process wirefilter (pid 28226): BEGIN
[20]: simulated_network: stop_monitoring the process wirefilter (pid 28226): SUCCESS
[20]: About to terminate the process with pid 28226...
[20]: SUCCESS: terminating the process with pid 28226 succeeded.
[20]: simulated_network: waitpid 28226 failed. (9)
[20]: process#spawn: the command line for wirefilter is:
---
  wirefilter -l LR0.000000 -D LR0.000000 --noise LR0 -d
  LR0.000000+0.000000 -l RL0.000000 -D RL0.000000 --noise RL0
  -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hub-socket-685773649:/tmp/marionnet-578881064.dir/hublet-0-socket-273367813
---
[20]: spawning process: a process (wirefilter) was just spawned (pid 28314).
[50]: *** Rebooting the wirefilter with pid 28314
[50]: simulated_network: stop_monitoring the process wirefilter (pid 28314): BEGIN
[50]: simulated_network: stop_monitoring the process wirefilter (pid 28314): SUCCESS
[50]: About to terminate the process with pid 28314...
[50]: SUCCESS: terminating the process with pid 28314 succeeded.
[50]: simulated_network: waitpid 28314 failed. (9)
[50]: process#spawn: the command line for wirefilter is:
---
  wirefilter -l LR0.000000 -D LR0.000000 --noise LR0 -d
  LR0.000000+0.000000 -l RL0.000000 -D RL0.000000 --noise RL0
  -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hub-socket-685773649:/tmp/marionnet-578881064.dir/hublet-0-socket-273367813
---
[50]: spawning process: a process (wirefilter) was just spawned (pid 28324).
[52]: *** Rebooting the wirefilter with pid 28324
[52]: simulated_network: stop_monitoring the process wirefilter (pid 28324): BEGIN
[52]: simulated_network: stop_monitoring the process wirefilter (pid 28324): SUCCESS
[52]: About to terminate the process with pid 28324...
[52]: SUCCESS: terminating the process with pid 28324 succeeded.
[52]: simulated_network: waitpid 28324 failed. (9)
[52]: process#spawn: the command line for wirefilter is:
---
  wirefilter -l LR0.000000 -D LR0.000000 --noise LR0 -d
  LR0.000000+0.000000 -l RL0.000000 -D RL0.000000 --noise RL0
  -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hub-socket-685773649:/tmp/marionnet-578881064.dir/hublet-0-socket-273367813
---
[52]: spawning process: a process (wirefilter) was just spawned (pid 28335).
[24]: *** Rebooting the wirefilter with pid 28232
[24]: simulated_network: stop_monitoring the process wirefilter (pid 28232): BEGIN
[24]: simulated_network: stop_monitoring the process wirefilter (pid 28232): SUCCESS
[24]: About to terminate the process with pid 28232...
[24]: SUCCESS: terminating the process with pid 28232 succeeded.
[24]: simulated_network: waitpid 28232 failed. (9)
[24]: process#spawn: the command line for wirefilter is:
---
  wirefilter -l LR0.000000 -D LR0.000000 --noise LR0 -d
  LR0.000000+0.000000 -l RL0.000000 -D RL0.000000 --noise RL0
  -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hub-socket-685773649:/tmp/marionnet-578881064.dir/hublet-2-socket-604961300
---
[24]: spawning process: a process (wirefilter) was just spawned (pid 28346).
[26]: *** Rebooting the wirefilter with pid 28235
[26]: simulated_network: stop_monitoring the process wirefilter (pid 28235): BEGIN
[26]: simulated_network: stop_monitoring the process wirefilter (pid 28235): SUCCESS
[26]: About to terminate the process with pid 28235...
[26]: SUCCESS: terminating the process with pid 28235 succeeded.
[26]: simulated_network: waitpid 28235 failed. (9)
[26]: process#spawn: the command line for wirefilter is:
---
  wirefilter -l LR0.000000 -D LR0.000000 --noise LR0 -d
  LR0.000000+0.000000 -l RL0.000000 -D RL0.000000 --noise RL0
  -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hub-socket-685773649:/tmp/marionnet-578881064.dir/hublet-3-socket-425713594
---
[26]: spawning process: a process (wirefilter) was just spawned (pid 28355).
[54]: *** Rebooting the wirefilter with pid 28335
[54]: simulated_network: stop_monitoring the process wirefilter (pid 28335): BEGIN
[54]: simulated_network: stop_monitoring the process wirefilter (pid 28335): SUCCESS
[54]: About to terminate the process with pid 28335...
[54]: SUCCESS: terminating the process with pid 28335 succeeded.
[54]: simulated_network: waitpid 28335 failed. (9)
[54]: process#spawn: the command line for wirefilter is:
---
  wirefilter -l LR0.000000 -D LR0.000000 --noise LR0 -d
  LR0.000000+0.000000 -l RL0.000000 -D RL0.000000 --noise RL0
  -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hub-socket-685773649:/tmp/marionnet-578881064.dir/hublet-0-socket-273367813
---
[54]: spawning process: a process (wirefilter) was just spawned (pid 28364).
[60]: *** Rebooting the wirefilter with pid 28364
[60]: simulated_network: stop_monitoring the process wirefilter (pid 28364): BEGIN
[60]: simulated_network: stop_monitoring the process wirefilter (pid 28364): SUCCESS
[60]: About to terminate the process with pid 28364...
[60]: SUCCESS: terminating the process with pid 28364 succeeded.
[60]: simulated_network: waitpid 28364 failed. (9)
[60]: process#spawn: the command line for wirefilter is:
---
  wirefilter -l LR0.000000 -D LR0.000000 --noise LR0 -d
  LR0.000000+0.000000 -l RL0.000000 -D RL0.000000 --noise RL0
  -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hub-socket-685773649:/tmp/marionnet-578881064.dir/hublet-0-socket-273367813
---
[60]: spawning process: a process (wirefilter) was just spawned (pid 28367).
[22]: *** Rebooting the wirefilter with pid 28229
[22]: simulated_network: stop_monitoring the process wirefilter (pid 28229): BEGIN
[22]: simulated_network: stop_monitoring the process wirefilter (pid 28229): SUCCESS
[22]: About to terminate the process with pid 28229...
[22]: SUCCESS: terminating the process with pid 28229 succeeded.
[22]: simulated_network: waitpid 28229 failed. (9)
[22]: process#spawn: the command line for wirefilter is:
---
  wirefilter -l LR0.000000 -D LR0.000000 --noise LR0 -d
  LR0.000000+0.000000 -l RL0.000000 -D RL0.000000 --noise RL0
  -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hub-socket-685773649:/tmp/marionnet-578881064.dir/hublet-1-socket-332149307
---
[22]: spawning process: a process (wirefilter) was just spawned (pid 28376).
[56]: *** Rebooting the wirefilter with pid 28346
[56]: simulated_network: stop_monitoring the process wirefilter (pid 28346): BEGIN
[56]: simulated_network: stop_monitoring the process wirefilter (pid 28346): SUCCESS
[56]: About to terminate the process with pid 28346...
[56]: SUCCESS: terminating the process with pid 28346 succeeded.
[56]: simulated_network: waitpid 28346 failed. (9)
[56]: process#spawn: the command line for wirefilter is:
---
  wirefilter -l LR0.000000 -D LR0.000000 --noise LR0 -d
  LR0.000000+0.000000 -l RL0.000000 -D RL0.000000 --noise RL0
  -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hub-socket-685773649:/tmp/marionnet-578881064.dir/hublet-2-socket-604961300
---
[56]: spawning process: a process (wirefilter) was just spawned (pid 28380).
^A[58]: *** Rebooting the wirefilter with pid 28355
[58]: simulated_network: stop_monitoring the process wirefilter (pid 28355): BEGIN
[58]: simulated_network: stop_monitoring the process wirefilter (pid 28355): SUCCESS
[58]: About to terminate the process with pid 28355...
[58]: SUCCESS: terminating the process with pid 28355 succeeded.
[58]: simulated_network: waitpid 28355 failed. (9)
[58]: process#spawn: the command line for wirefilter is:
---
  wirefilter -l LR0.000000 -D LR0.000000 --noise LR0 -d
  LR0.000000+0.000000 -l RL0.000000 -D RL0.000000 --noise RL0
  -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hub-socket-685773649:/tmp/marionnet-578881064.dir/hublet-3-socket-425713594
---
[58]: spawning process: a process (wirefilter) was just spawned (pid 28389).
[68]: *** Rebooting the wirefilter with pid 28389
[68]: simulated_network: stop_monitoring the process wirefilter (pid 28389): BEGIN
[68]: simulated_network: stop_monitoring the process wirefilter (pid 28389): SUCCESS
[68]: About to terminate the process with pid 28389...
[68]: SUCCESS: terminating the process with pid 28389 succeeded.
[68]: simulated_network: waitpid 28389 failed. (9)
[68]: process#spawn: the command line for wirefilter is:
---
  wirefilter -l LR0.000000 -D LR0.000000 --noise LR0 -d
  LR0.000000+0.000000 -l RL0.000000 -D RL0.000000 --noise RL0
  -d RL0.000000+0.000000 -v
  /tmp/marionnet-578881064.dir/hub-socket-685773649:/tmp/marionnet-578881064.dir/hublet-3-socket-425713594
---
[68]: spawning process: a process (wirefilter) was just spawned (pid 28394).

<--snap-->

Maybe this helps getting closer to what is causing the problem.

Thanks in advance!

Question information

Language:
English Edit question
Status:
Answered
For:
marionnet Edit question
Assignee:
No assignee Edit question
Last query:
2012-04-27
Last reply:
2012-05-02
Luca Saiu (saiu) said : #1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk+avpgACgkQvzOavibF0ob7RACfUr8dbcEMmRwE2Ga1IzU+aOji
5AgAn0ucRM9WVW34erT1MJ+DTOr0kIUe
=SoEo
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello.

You installed via the script, so this problem is a little surprising for
us. We suspect that your distribution doesn't respect some assumption
in the script; such problems are particularly important for us since
Marionnet is aimed at beginners as well, so we definitely want to fix
the bug.

Can you please give us some information about your system? What is the
name and version of your distribution?

Please tell us the output of:
- --8<---------------cut here---------------start------------->8---
uname -a
cat /etc/issue
- --8<---------------cut here---------------end--------------->8---

What happens if you just create a couple of hubs and you connect them
with a cable, with *no* computers all? Can you please confirm that such a
network can be started up?

Thanks,

- --
Luca Saiu
Home page: http://www-lipn.univ-paris13.fr/~saiu
My blog: http://ageinghacker.net/blog
GNU epsilon: http://www.gnu.org/software/epsilon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk+avpsACgkQvzOavibF0oZmNACgpVJatF6bUe4Hl6ArpqoQko5E
Wn8AmweblsC7VOPdsRpTWbEzOzT16i3N
=jHZ/
-----END PGP SIGNATURE-----

Michele (mick89-mac) said : #2

I've got the same problem, when I try so start a pc, an hub, or anything else I get the same error: "a process died unexpectedly".
I installed marionnet from the script and my specs are:
Linux notebook 3.3.4-custom #1 SMP Tue May 1 11:14:15 CEST 2012 x86_64 GNU/Linux
Linux Mint Xfce Edition \n \l

thanks in advance.

Michele

Just one question : are you able to execute 32bits binary executables ?
(Marionnet comes with 32bits kernels for the virtual machines);
on ubuntu 64 bits I had to add some compatiblity package
I think it was

ia32-libs

F. Butelle

Le 02/05/2012 13:30, Michele a écrit :
> Question #194941 on marionnet changed:
> https://answers.launchpad.net/marionnet/+question/194941
>
> Michele requested more information:
> I've got the same problem, when I try so start a pc, an hub, or anything else I get the same error: "a process died unexpectedly".
> I installed marionnet from the script and my specs are:
> Linux notebook 3.3.4-custom #1 SMP Tue May 1 11:14:15 CEST 2012 x86_64 GNU/Linux
> Linux Mint Xfce Edition \n \l
>
> thanks in advance.
>
> Michele
>

Michele (mick89-mac) said : #4

Thanks a lot, it solved the problem!

Michele

Can you help with this problem?

Provide an answer of your own, or ask kern for more information if necessary.

To post a message you must log in.