Package: cfengine3 Version: 3.0.5+dfsg-1 Severity: normal *** Please type your report below this line ***
Hello, I recently began my cf3 deployment on a few Debian machines and I managed to hit a case when having some locks present triggers a segmentation fault. How to reproduce: - get the COPBL library from http://source.cfengine.com/browse/copbl/trunk/cfengine_stdlib.cf and comment the cmd_repair body as it doesn't work with 3.0 (I used r110, just in case); - use the following promises.cf: ======== from here ======== body common control { bundlesequence => { "debs" }; inputs => { "cfengine_stdlib.cf" }; } bundle agent debs { packages: "cfengine3" package_policy => "add", package_method => generic; } ========= to here ========= - run cf-agent -I once, observe that it does run aptitude update properly; - run cf-agent -I again, watch it segfault; - run cf-agent -KI, it works. Strace ends with: ======== from here ======== ... open("/var/lib/cfengine3/state/cf_lock.db", O_RDWR|O_CREAT, 0) = 3 fcntl(3, F_GETFD) = 0 fcntl(3, F_SETFD, FD_CLOEXEC) = 0 fstat(3, {st_mode=S_IFREG|0644, st_size=8192, ...}) = 0 pread(3, "\0\0\0\0\1\0\0\0\0\0\0\0b1\5\0\t\0\0\0\0\20\0\0\0\t\0\0\0\0\0\0"..., 4096, 0) = 4096 --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++ Segmentation fault ========= to here ========= I'll see if I can narrow it down further and reply to this bug. -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cfengine3 depends on: ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libdb4.8 4.8.30-2 Berkeley v4.8 Database Libraries [ ii libpcre3 8.02-1.1 Perl 5 Compatible Regular Expressi ii libssl0.9.8 0.9.8o-4squeeze7 SSL shared libraries cfengine3 recommends no packages. cfengine3 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
