Trace number 320964

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
Hybrid1 2007-02-08UNSAT 1.00485 1.00693

General information on the benchmark

Nameindustrial/babic/xinetd/
xinetd_vc56703.cnf
MD5SUM09053ffc48c8fbc3352a0ce4d89c2bbb
Bench CategoryINDUST (industrial instances)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.193969
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 (download as text)

0.89/1.00	c A contradiction is found at top!
0.89/1.00	s UNSATISFIABLE

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node61/watcher-320964-1176325684 -o ROOT/results/node61/solver-320964-1176325684 -C 1200 -W 2400 -M 1800 --output-limit 1,15 /tmp/evaluation/320964-1176325684/Hybrid1 /tmp/evaluation/320964-1176325684/instance-320964-1176325684.cnf 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1200 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1230 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2400 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 1843200 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 1894400 KiB
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 8968
/proc/meminfo: memFree=1805680/2055920 swapFree=4192812/4192956
[pid=8968] ppid=8966 vsize=244720 CPUtime=0
/proc/8968/stat : 8968 (Hybrid1) R 8966 8968 6839 0 -1 4194304 114 0 0 0 0 0 0 0 18 0 1 0 44532051 250593280 98 18446744073709551615 134512640 134935932 4294956592 18446744073709551615 134521424 0 0 4096 0 0 0 0 17 1 0 0
/proc/8968/statm: 61180 99 39 103 0 60684 0

[startup+0.00652796 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 8968
/proc/meminfo: memFree=1805680/2055920 swapFree=4192812/4192956
[pid=8968] ppid=8966 vsize=244852 CPUtime=0
/proc/8968/stat : 8968 (Hybrid1) R 8966 8968 6839 0 -1 4194304 134 0 0 0 0 0 0 0 18 0 1 0 44532051 250728448 118 18446744073709551615 134512640 134935932 4294956592 18446744073709551615 134588695 0 0 4096 0 0 0 0 17 1 0 0
/proc/8968/statm: 61213 119 39 103 0 60717 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 244852

[startup+0.101535 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 8968
/proc/meminfo: memFree=1805680/2055920 swapFree=4192812/4192956
[pid=8968] ppid=8966 vsize=246304 CPUtime=0.09
/proc/8968/stat : 8968 (Hybrid1) R 8966 8968 6839 0 -1 4194304 758 0 0 0 9 0 0 0 18 0 1 0 44532051 252215296 742 18446744073709551615 134512640 134935932 4294956592 18446744073709551615 134521553 0 0 4096 0 0 0 0 17 1 0 0
/proc/8968/statm: 61576 742 39 103 0 61080 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 246304

[startup+0.301553 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 8968
/proc/meminfo: memFree=1805680/2055920 swapFree=4192812/4192956
[pid=8968] ppid=8966 vsize=249472 CPUtime=0.29
/proc/8968/stat : 8968 (Hybrid1) R 8966 8968 6839 0 -1 4194304 2015 0 0 0 28 1 0 0 19 0 1 0 44532051 255459328 1999 18446744073709551615 134512640 134935932 4294956592 18446744073709551615 134588695 0 0 4096 0 0 0 0 17 1 0 0
/proc/8968/statm: 62368 1999 39 103 0 61872 0
Current children cumulated CPU time (s) 0.29
Current children cumulated vsize (KiB) 249472

[startup+0.701591 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 8968
/proc/meminfo: memFree=1805680/2055920 swapFree=4192812/4192956
[pid=8968] ppid=8966 vsize=262800 CPUtime=0.69
/proc/8968/stat : 8968 (Hybrid1) R 8966 8968 6839 0 -1 4194304 6279 0 0 0 67 2 0 0 23 0 1 0 44532051 269107200 6261 18446744073709551615 134512640 134935932 4294956592 18446744073709551615 134523514 0 0 4096 0 0 0 0 17 1 0 0
/proc/8968/statm: 65700 6261 40 103 0 65204 0
Current children cumulated CPU time (s) 0.69
Current children cumulated vsize (KiB) 262800

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

[startup+0.901611 s]
/proc/loadavg: 0.91 0.97 0.99 3/64 8968
/proc/meminfo: memFree=1805680/2055920 swapFree=4192812/4192956
[pid=8968] ppid=8966 vsize=262800 CPUtime=0.89
/proc/8968/stat : 8968 (Hybrid1) R 8966 8968 6839 0 -1 4194304 6279 0 0 0 87 2 0 0 24 0 1 0 44532051 269107200 6261 18446744073709551615 134512640 134935932 4294956592 18446744073709551615 134523624 0 0 4096 0 0 0 0 17 1 0 0
/proc/8968/statm: 65700 6261 40 103 0 65204 0
Current children cumulated CPU time (s) 0.89
Current children cumulated vsize (KiB) 262800

[startup+1.00162 s]
/proc/loadavg: 0.91 0.97 0.99 2/65 8969
/proc/meminfo: memFree=1782888/2055920 swapFree=4192812/4192956
[pid=8968] ppid=8966 vsize=0 CPUtime=1
/proc/8968/stat : 8968 (Hybrid1) D 8966 8968 6839 0 -1 4194308 6663 0 0 0 97 3 0 0 25 0 1 0 44532051 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 0 18446744072100051646 0 0 17 1 0 0
/proc/8968/statm: 0 0 0 0 0 0 0
Current children cumulated CPU time (s) 1
Current children cumulated vsize (KiB) 0

Child status: 20
Real time (s): 1.00693
CPU time (s): 1.00485
CPU user time (s): 0.973851
CPU system time (s): 0.030995
CPU usage (%): 99.7934
Max. virtual memory (cumulated for all children) (KiB): 262800

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

runsolver used 0.005999 second user time and 0.006998 second system time

The end

Launcher Data (download as text)

Begin job on node61 on Wed Apr 11 21:08:04 UTC 2007

IDJOB= 320964
IDBENCH= 20516
IDSOLVER= 115
FILE ID= node61/320964-1176325684

PBS_JOBID= 4516706

Free space on /tmp= 66554 MiB

SOLVER NAME= Hybrid1 2007-02-08
BENCH NAME= HOME/pub/bench/SAT07/industrial/babic/xinetd/xinetd_vc56703.cnf
COMMAND LINE= /tmp/evaluation/320964-1176325684/Hybrid1 /tmp/evaluation/320964-1176325684/instance-320964-1176325684.cnf            
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node61/watcher-320964-1176325684 -o ROOT/results/node61/solver-320964-1176325684 -C 1200 -W 2400 -M 1800 --output-limit 1,15  /tmp/evaluation/320964-1176325684/Hybrid1 /tmp/evaluation/320964-1176325684/instance-320964-1176325684.cnf            

META MD5SUM SOLVER= 4ad8950502569bcbd9dc3ae819b6eefe
MD5SUM BENCH=  09053ffc48c8fbc3352a0ce4d89c2bbb

RANDOM SEED= 284066593

TIME LIMIT= 1200 seconds
MEMORY LIMIT= 1800 MiB

Linux node61.alineos.net 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005 x86_64 x86_64 x86_64 GNU/Linux

/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.240
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.240
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:       1806216 kB
Buffers:         11620 kB
Cached:         126352 kB
SwapCached:          0 kB
Active:          81280 kB
Inactive:        81288 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1806216 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           11236 kB
Writeback:           0 kB
Mapped:          34760 kB
Slab:            73296 kB
Committed_AS:   103276 kB
PageTables:       1408 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= 66554 MiB

End job on node61 on Wed Apr 11 21:08:05 UTC 2007