Trace number 1776427

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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
ManySAT 1.1 aimd 2/2009-03-20 (4 threads)UNSAT 0.26 0.257193

General information on the benchmark

Nameindustrial/babic/xinetd/
xinetd_vc56703.cnf
MD5SUM09053ffc48c8fbc3352a0ce4d89c2bbb
Bench CategoryAPPLICATION (applications instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.26
Satisfiable
(Un)Satisfiability was proved
Number of variables110923
Number of clauses286428
Sum of the clauses size694958
Maximum clause length3
Minimum clause length1
Number of clauses of size 113085
Number of clauses of size 2138156
Number of clauses of size 3135187
Number of clauses of size 40
Number of clauses of size 50
Number of clauses of size over 50

Solver Data 

0.00/0.00	c Parsing...
0.00/0.22	c ==============================================================================
0.00/0.22	c |           |     ORIGINAL     |              LEARNT              |          |
0.00/0.22	c | Conflicts | Clauses Literals |   Limit Clauses Literals  Lit/Cl | Progress |
0.00/0.22	c ==============================================================================
0.00/0.22	c |         0 |  270567   676320 |   81170       0        0     nan |  0.000 % |
0.00/0.25	c (contradiction during subsumption)
0.00/0.25	c starts                :        0
0.00/0.25	c conflicts             :        0   (0 /sec)
0.00/0.25	c reduce learnts        :        0   (0 /sec)
0.00/0.25	c decisions             :        0   (0 /sec)
0.00/0.25	c propagations          :        0   (0 /sec)
0.00/0.25	c inspects              :        0   (0 /sec)
0.00/0.25	c memory used           :  41.3359 MB
0.00/0.25	c CPU time              :     0.22 s
0.00/0.25	c 
0.00/0.25	s UNSATISFIABLE

Verifier Data 

No possible verification on an UNSAT instance

Watcher Data 

runsolver version 3.2.9 (svn:503) (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w /tmp/evaluation-result-1776427-1243509514/watcher-1776427-1243509514 -o /tmp/evaluation-result-1776427-1243509514/solver-1776427-1243509514 -C 10000 -W 1000 -M 2047 manysat.sh HOME/instance-1776427-1243509514.cnf aimd 2 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 10000 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 10030 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 1000 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 2096128 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 2147328 KiB
Current StackSize limit: 8192 KiB


[startup+0 s]
/proc/loadavg: 4.22 4.24 4.25 3/96 1875
/proc/meminfo: memFree=3130960/3368532 swapFree=1953788/1959888
[pid=1875] ppid=1873 vsize=2412 CPUtime=0
/proc/1875/stat : 1875 (manysat.sh) R 1873 1875 27966 0 -1 4194304 335 0 0 0 0 0 0 0 18 0 1 0 1115615488 2469888 274 4294967295 134512640 135169312 3214400704 3214399180 3085256564 0 65538 4 65536 0 0 0 17 2 0 0 0
/proc/1875/statm: 603 274 231 161 0 42 0

[startup+0.074254 s]
/proc/loadavg: 4.22 4.24 4.25 3/96 1875
/proc/meminfo: memFree=3130960/3368532 swapFree=1953788/1959888
[pid=1875] ppid=1873 vsize=2412 CPUtime=0
/proc/1875/stat : 1875 (manysat.sh) S 1873 1875 27966 0 -1 4194304 350 0 0 0 0 0 0 0 18 0 1 0 1115615488 2469888 274 4294967295 134512640 135169312 3214400704 3214399240 3085254382 0 65536 4 65538 3222376037 0 0 17 2 0 0 0
/proc/1875/statm: 603 274 231 161 0 42 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 2412

[startup+0.104171 s]
/proc/loadavg: 4.22 4.24 4.25 3/96 1875
/proc/meminfo: memFree=3130960/3368532 swapFree=1953788/1959888
[pid=1875] ppid=1873 vsize=2412 CPUtime=0
/proc/1875/stat : 1875 (manysat.sh) S 1873 1875 27966 0 -1 4194304 350 0 0 0 0 0 0 0 18 0 1 0 1115615488 2469888 274 4294967295 134512640 135169312 3214400704 3214399240 3085254382 0 65536 4 65538 3222376037 0 0 17 2 0 0 0
/proc/1875/statm: 603 274 231 161 0 42 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 2412

Solver just ended. Dumping a history of the last processes samples

[startup+0.204163 s]
/proc/loadavg: 4.22 4.24 4.25 3/96 1875
/proc/meminfo: memFree=3130960/3368532 swapFree=1953788/1959888
[pid=1875] ppid=1873 vsize=2412 CPUtime=0
/proc/1875/stat : 1875 (manysat.sh) S 1873 1875 27966 0 -1 4194304 350 0 0 0 0 0 0 0 18 0 1 0 1115615488 2469888 274 4294967295 134512640 135169312 3214400704 3214399240 3085254382 0 65536 4 65538 3222376037 0 0 17 2 0 0 0
/proc/1875/statm: 603 274 231 161 0 42 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 2412

Child status: 20
Real time (s): 0.257193
CPU time (s): 0.26
CPU user time (s): 0.23
CPU system time (s): 0.03
CPU usage (%): 101.091
Max. virtual memory (cumulated for all children) (KiB): 2412

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.23
system time used= 0.03
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 10246
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= 4
involuntary context switches= 2

runsolver used 0 second user time and 0.01 second system time

The end

Launcher Data 

Begin job on  at 2009-05-28 13:18:34
IDJOB=1776427
IDBENCH=20516
IDSOLVER=626
FILE ID=/1776427-1243509514
PBS_JOBID=
Free space on /tmp= 6471 MiB

SOLVER NAME= ManySAT 1.1 aimd 2/2009-03-20 (4 threads)
BENCH NAME= SAT07/industrial/babic/xinetd/xinetd_vc56703.cnf
COMMAND LINE= manysat.sh BENCHNAME aimd 2
RUNSOLVER COMMAND LINE= runsolver --timestamp  -w /tmp/evaluation-result-1776427-1243509514/watcher-1776427-1243509514 -o /tmp/evaluation-result-1776427-1243509514/solver-1776427-1243509514 -C 10000 -W 1000 -M 2047  manysat.sh HOME/instance-1776427-1243509514.cnf aimd 2

TIME LIMIT= 10000 seconds
MEMORY LIMIT= 2047 MiB
MAX NB THREAD= 4

MD5SUM BENCH= 09053ffc48c8fbc3352a0ce4d89c2bbb
RANDOM SEED= 1227859659

Linux (none) 2.6.21.5 #6 SMP Wed Jul 4 17:16:38 CEST 2007 i686 GNU/Linux

/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz
stepping	: 6
cpu MHz		: 1995.061
cache size	: 4096 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
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 pbe lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm
bogomips	: 3992.41
clflush size	: 64

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz
stepping	: 6
cpu MHz		: 1995.061
cache size	: 4096 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
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 pbe lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm
bogomips	: 3990.12
clflush size	: 64

processor	: 2
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz
stepping	: 6
cpu MHz		: 1995.061
cache size	: 4096 KB
physical id	: 3
siblings	: 2
core id		: 0
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
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 pbe lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm
bogomips	: 3990.14
clflush size	: 64

processor	: 3
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Xeon(R) CPU            5130  @ 2.00GHz
stepping	: 6
cpu MHz		: 1995.061
cache size	: 4096 KB
physical id	: 3
siblings	: 2
core id		: 1
cpu cores	: 2
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
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 pbe lm constant_tsc pni monitor ds_cpl vmx tm2 ssse3 cx16 xtpr dca lahf_lm
bogomips	: 3990.14
clflush size	: 64


/proc/meminfo:
MemTotal:      3368532 kB
MemFree:       3130960 kB
Buffers:         38188 kB
Cached:          99348 kB
SwapCached:       2256 kB
Active:          70676 kB
Inactive:        76444 kB
HighTotal:     2489216 kB
HighFree:      2378848 kB
LowTotal:       879316 kB
LowFree:        752112 kB
SwapTotal:     1959888 kB
SwapFree:      1953788 kB
Dirty:            6908 kB
Writeback:           0 kB
AnonPages:        8840 kB
Mapped:           3232 kB
Slab:            80744 kB
SReclaimable:    67248 kB
SUnreclaim:      13496 kB
PageTables:        464 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:   3644152 kB
Committed_AS:    88684 kB
VmallocTotal:   114680 kB
VmallocUsed:      1444 kB
VmallocChunk:   113072 kB

Free space on /tmp at the end= 6471 MiB
End job on  at 2009-05-28 13:18:34