Trace number 282649

Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided into four (or five) parts:
  1. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds, and are wall clock time (not CPU time).

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to X seconds (see the parameters in the trace). After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  5. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerCPU timeWall clock time
Toolbar_MaxSat 2007-01-19? (MO) 1.07 1.15279

General information on the benchmark

NameMaxCSP/celar/scens/
scenw-06-16_ext.xml
MD5SUMc07618a7c18950ed01e14a653b4f1e99
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of satisfied constraints1197
Best CPU time to get the best result obtained on this benchmark57.7422
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints1222
Maximum constraint arity2
Maximum domain size28
Number of constraints which are defined in extension1222
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c conversion script
c 
c 

translate /tmp/evaluation/282649-1169321149/unknown.xml to /tmp/evaluation/282649-1169321149/unknown.wcsp

Verifier Data (download as text)

ERROR: no interpretation found !

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node1/watcher-282649-1169321149 -o ROOT/results/node1/solver-282649-1169321149 -C 2400 -M 900 /tmp/evaluation/282649-1169321149/solver.sh /tmp/evaluation/282649-1169321149/unknown 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 2400 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 2430 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Current StackSize limit: 10240 KiB

/proc/loadavg: 1.94 1.99 1.99 2/88 22178
/proc/meminfo: memFree=1260232/2055920 swapFree=4165612/4192956
[pid=22177] ppid=22175 vsize=8560 CPUtime=0
/proc/22177/stat : 22177 (solver.sh) R 22175 22177 22093 0 -1 4194304 308 0 0 0 0 0 0 0 20 0 1 0 280510858 8765440 253 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 259353462671 0 0 4096 8192 0 0 0 17 1 0 0
/proc/22177/statm: 2140 253 197 79 0 133 0

[startup+0.105493 s]
/proc/loadavg: 1.94 1.99 1.99 2/88 22178
/proc/meminfo: memFree=1260232/2055920 swapFree=4165612/4192956
[pid=22177] ppid=22175 vsize=47568 CPUtime=0.01
/proc/22177/stat : 22177 (solver.sh) S 22175 22177 22093 0 -1 4194304 876 2245 0 0 0 0 0 1 21 0 1 0 280510858 48709632 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 259352882010 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/22177/statm: 11892 361 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47568

[startup+0.516541 s]
/proc/loadavg: 1.94 1.99 1.99 2/88 22178
/proc/meminfo: memFree=1260232/2055920 swapFree=4165612/4192956
[pid=22177] ppid=22175 vsize=47568 CPUtime=0.33
/proc/22177/stat : 22177 (solver.sh) S 22175 22177 22093 0 -1 4194304 905 3192 0 0 0 0 30 3 15 0 1 0 280510858 48709632 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 259352882010 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/22177/statm: 11892 361 245 79 0 217 0
Current children cumulated CPU time (s) 0.33
Current children cumulated vsize (KiB) 47568



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+1.13463 s]
/proc/loadavg: 1.94 1.99 1.99 4/89 22199
/proc/meminfo: memFree=843456/2055920 swapFree=4165612/4192956
[pid=22177] ppid=22175 vsize=47568 CPUtime=0.33
/proc/22177/stat : 22177 (solver.sh) S 22175 22177 22093 0 -1 4194304 905 3192 0 0 0 0 30 3 15 0 1 0 280510858 48709632 361 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 259352882010 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/22177/statm: 11892 361 245 79 0 217 0
[pid=22196] ppid=22177 vsize=877168 CPUtime=0.74
/proc/22196/stat : 22196 (toolbar) R 22177 22177 22093 0 -1 4194304 103093 3092 0 0 2 42 29 1 20 0 1 0 280510895 898220032 103059 18446744073709551615 134512640 135242688 4294956608 18446744073709551615 134580758 0 0 4096 0 0 0 0 17 1 0 0
/proc/22196/statm: 219292 103059 54 178 0 219110 0
Current children cumulated CPU time (s) 1.07
Current children cumulated vsize (KiB) 924736

Sending SIGTERM to process tree (bottom up)

Child ended because it received signal 15 (SIGTERM)

!!! problem with CPU time !!!
wait4(...,&childrusage) returns 22177 and gives childrusage.ru_utime.tv_sec=0 childrusage.ru_utime.tv_usec=311952 childrusage.ru_stime.tv_sec=0 childrusage.ru_stime.tv_usec=42993
CPU time returned by wait4() is 0.354945
while last known CPU time is 1.07

Solver probably didn't/couldn't wait for its children
Using last known CPU time as value...

Real time (s): 1.15279
CPU time (s): 1.07
CPU user time (s): 0.61
CPU system time (s): 0.46
CPU usage (%): 92.8182
Max. virtual memory (cumulated for all children) (KiB): 924736

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.311952
system time used= 0.042993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4097
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 65
involuntary context switches= 41

runsolver used 0.005999 s user time and 0.014997 s system time

The end

Launcher Data (download as text)

Begin job on node1 on Sat Jan 20 19:25:49 UTC 2007


IDJOB= 282649
IDBENCH= 12874
IDSOLVER= 71
FILE ID= node1/282649-1169321149

PBS_JOBID= 3610083

Free space on /tmp= 66552 MiB

SOLVER NAME= Toolbar_MaxSat 2007-01-19
BENCH NAME= HOME/pub/bench/CPAI06/MaxCSP/celar/scens/scenw-06-16_ext.xml
COMMAND LINE= /tmp/evaluation/282649-1169321149/solver.sh /tmp/evaluation/282649-1169321149/unknown
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node1/convwatcher-282649-1169321149 -o ROOT/results/node1/conversion-282649-1169321149 -C 600 -M 900 /tmp/evaluation/282649-1169321149/translate /tmp/evaluation/282649-1169321149/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node1/watcher-282649-1169321149 -o ROOT/results/node1/solver-282649-1169321149 -C 2400 -M 900  /tmp/evaluation/282649-1169321149/solver.sh /tmp/evaluation/282649-1169321149/unknown

META MD5SUM SOLVER= f843f34905a307bcc0c6a322bc802c9d
MD5SUM BENCH=  c07618a7c18950ed01e14a653b4f1e99

RANDOM SEED= 785947784

TIME LIMIT= 2400 seconds

MEMORY LIMIT= 900 MiB


/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.234
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.234
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1260904 kB
Buffers:         55288 kB
Cached:         606944 kB
SwapCached:       4372 kB
Active:         321180 kB
Inactive:       395376 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1260904 kB
SwapTotal:     4192956 kB
SwapFree:      4165612 kB
Dirty:            4760 kB
Writeback:           0 kB
Mapped:          65360 kB
Slab:            63140 kB
Committed_AS:  8733220 kB
PageTables:       2384 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66547 MiB



End job on node1 on Sat Jan 20 19:25:52 UTC 2007