Trace number 1773197

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
MXC 2009-03-10UNSAT 0.292954 0.293904

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.241962
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.19/0.28	c starting MXC with:
0.19/0.28	c cnf_path = HOME/instance-1773197-1241298808.cnf
0.19/0.28	c restart_strategy = auto
0.19/0.28	c sign_strategy = cached
0.19/0.28	c use_preprocessing = -1
0.19/0.28	c output_implicant = 1
0.19/0.28	c timeout_seconds = 0
0.19/0.28	c ===================================[MXC]=====================================
0.19/0.28	c | Conflicts |                Clause Statistics                   |   Vars   |
0.19/0.28	c |           |    CARD     BIN      O3+      L3+   L3+Lim  Lit/CL |          |
0.19/0.28	c =============================================================================
0.19/0.28	c |         0 |       0       0        0        0        0     nan |   110923 |
0.19/0.28	c ----- stats for thread 0 -----
0.19/0.28	c restarts: 0
0.19/0.28	c decisions: 0
0.19/0.28	c propagations: 0
0.19/0.28	c conflicts: 0
0.19/0.28	c 0.278s elapsed
0.19/0.28	s UNSATISFIABLE

Verifier Data

No possible verification on an UNSAT instance

Watcher Data

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

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-1773197-1241298808/watcher-1773197-1241298808 -o /tmp/evaluation-result-1773197-1241298808/solver-1773197-1241298808 -C 10000 -W 12000 -M 1800 HOME/mxc-sat09 -i HOME/instance-1773197-1241298808.cnf 

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): 12000 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
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 1.13 2.60 3.39 3/64 25858
/proc/meminfo: memFree=1932096/2055920 swapFree=4181456/4192956
[pid=25858] ppid=25856 vsize=5828 CPUtime=0
/proc/25858/stat : 25858 (mxc-sat09) R 25856 25858 25794 0 -1 4194304 744 0 0 0 0 0 0 0 18 0 1 0 157913835 5967872 731 1992294400 134512640 135192793 4294956224 18446744073709551615 134779278 0 0 4096 0 0 0 0 17 1 0 0
/proc/25858/statm: 1457 737 46 166 0 1288 0

[startup+0.074023 s]
/proc/loadavg: 1.13 2.60 3.39 3/64 25858
/proc/meminfo: memFree=1932096/2055920 swapFree=4181456/4192956
[pid=25858] ppid=25856 vsize=31488 CPUtime=0.07
/proc/25858/stat : 25858 (mxc-sat09) R 25856 25858 25794 0 -1 4194304 6384 0 0 0 4 3 0 0 18 0 1 0 157913835 32243712 6368 1992294400 134512640 135192793 4294956224 18446744073709551615 134750438 0 0 4096 0 0 0 0 17 1 0 0
/proc/25858/statm: 7872 6369 55 166 0 7703 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 31488

[startup+0.101026 s]
/proc/loadavg: 1.13 2.60 3.39 3/64 25858
/proc/meminfo: memFree=1932096/2055920 swapFree=4181456/4192956
[pid=25858] ppid=25856 vsize=33484 CPUtime=0.09
/proc/25858/stat : 25858 (mxc-sat09) R 25856 25858 25794 0 -1 4194304 6864 0 0 0 6 3 0 0 18 0 1 0 157913835 34287616 6848 1992294400 134512640 135192793 4294956224 18446744073709551615 134750438 0 0 4096 0 0 0 0 17 1 0 0
/proc/25858/statm: 8371 6849 55 166 0 8202 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 33484

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

[startup+0.201042 s]
/proc/loadavg: 1.13 2.60 3.39 3/64 25858
/proc/meminfo: memFree=1932096/2055920 swapFree=4181456/4192956
[pid=25858] ppid=25856 vsize=40956 CPUtime=0.19
/proc/25858/stat : 25858 (mxc-sat09) R 25856 25858 25794 0 -1 4194304 8670 0 0 0 15 4 0 0 18 0 1 0 157913835 41938944 8654 1992294400 134512640 135192793 4294956224 18446744073709551615 134750438 0 0 4096 0 0 0 0 17 1 0 0
/proc/25858/statm: 10239 8655 55 166 0 10070 0
Current children cumulated CPU time (s) 0.19
Current children cumulated vsize (KiB) 40956

Child status: 20
Real time (s): 0.293904
CPU time (s): 0.292954
CPU user time (s): 0.238963
CPU system time (s): 0.053991
CPU usage (%): 99.6768
Max. virtual memory (cumulated for all children) (KiB): 40956

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

runsolver used 0.002999 second user time and 0.008998 second system time

The end

Launcher Data

Begin job on node26 at 2009-05-02 23:13:29
IDJOB=1773197
IDBENCH=20516
IDSOLVER=613
FILE ID=node26/1773197-1241298808
PBS_JOBID= 9225187
Free space on /tmp= 66504 MiB

SOLVER NAME= MXC 2009-03-10
BENCH NAME= SAT07/industrial/babic/xinetd/xinetd_vc56703.cnf
COMMAND LINE= HOME/mxc-sat09 -i BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-1773197-1241298808/watcher-1773197-1241298808 -o /tmp/evaluation-result-1773197-1241298808/solver-1773197-1241298808 -C 10000 -W 12000 -M 1800  HOME/mxc-sat09 -i HOME/instance-1773197-1241298808.cnf

TIME LIMIT= 10000 seconds
MEMORY LIMIT= 1800 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 09053ffc48c8fbc3352a0ce4d89c2bbb
RANDOM SEED=2147015176

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

/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.261
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.261
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:       1932512 kB
Buffers:         12248 kB
Cached:          44896 kB
SwapCached:       5144 kB
Active:          30604 kB
Inactive:        34176 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1932512 kB
SwapTotal:     4192956 kB
SwapFree:      4181456 kB
Dirty:            5680 kB
Writeback:           0 kB
Mapped:          13544 kB
Slab:            44660 kB
Committed_AS:   666780 kB
PageTables:       1368 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= 66504 MiB
End job on node26 at 2009-05-02 23:13:29