Package: polipo
Version: 1.0.4-1+lenny1
Severity: minor
/etc/init.d/polipo status
returns:
Usage: /etc/init.d/polipo {start|stop|restart|force-reload}
Status is a standard operand for init scripts.
Without it, one cannot easily determine whether the polipo daemon is running
normally.
-- System
any ideas here? php-cgi continues to segfault. until this problem,
this has been a more or less rock solid server. now it's not. :-/
On Sat, Feb 27, 2010 at 2:23 PM, Count László de Almásy
wrote:
> here's a new backtrace (after installing php5-dbg)
>
> Program rece
here's a new backtrace (after installing php5-dbg)
Program received signal SIGSEGV, Segmentation fault.
zend_hash_destroy (ht=0x1000701)
at /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/Zend/zend_hash.c:712
712 /build/buildd-php5_5.3.1-5-amd64-M9dAcL/php5-5.3.1/Zend/zend_hash.c:
No su
and yet another one:
Program received signal SIGSEGV, Segmentation fault.
0x00698277 in zend_hash_destroy ()
(gdb) bt
#0 0x00698277 in zend_hash_destroy ()
#1 0x00719575 in ?? ()
#2 0x00715886 in ?? ()
#3 0x00643a22 in sapi_deactivate ()
#4 0x00
ok, some helpful person showed me how to do 'attach' to a pid with
gdb, so i'm now able to monitor the php-cgi processes. here's an
initial backtrace. is this helpful?
Program received signal SIGSEGV, Segmentation fault.
0x00698277 in zend_hash_destroy ()
(gdb) bt
#0 0x00698277 in
On Wed, Feb 24, 2010 at 3:56 PM, Ondřej Surý wrote:
> We still need the backtrace. Without a backtrace your report is almost
> useless.
i just can't figure out how to do that. i've spent a considerable
amount of time trying, but all the methods seem to assume either that
i'm running apache, or t
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31-1-amd64 (SMP w/4 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
of course, just as i say that (even though i waited 24 hours) i got a
couple more segfaults. :-/
so, php-cgi is still segfaulting, even with all package dependencies
for php-cgi and php-mysql current.
Feb 24 14:16:27 kernel: [9904871.496277] php-cgi[3520]: segfault at
1000701 ip 7fdba3cedb10
i found the segfault was related to libc, so i updated that package
and the other dependencies of php-cgi, and that seems to have fixed
the segfaults.
--
Cheers, László
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact list
On Mon, Feb 22, 2010 at 3:15 AM, Ondřej Surý wrote:
> - your system information (f.e. output of "reportbug --template
> libapache2-mod-php5")
System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kerne
something is rotten in Denmark bro.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
i've started to see this problem after upgrading to version 5.3.1-4 of
this package. it's very easy to reproduce, just by browsing around one
of my wordpress sites. i see the following in my syslog:
Feb 21 13:28:55 farc kernel: [9642819.574930] php-cgi[18295]: segfault
at 1000721 ip 006982
Thanks for the advice. Just changing the option name, but using the old
pattern syntax, didn't work in all cases, though.
I created a better testcase:
# mkdir -p /tmp/clamtest/test1 /tmp/clamtest/kde-htest
# mkdir -p /clamtest/test1
# touch /tmp/clamtest/test1/clamtest.test1.sample.file
# cp /tm
3:46:10 athlon login[14772]: pam_mount(misc.c:38):
set_myuid: (uid=0, euid=0, gid=615, egid=615)
3817 Aug 28 23:46:10 athlon login[26999]: pam_mount(pam_mount.c:418):
pmvarrun says login count is 1
3818 Aug 28 23:46:11 athlon login[26999]: pam_mount(pam_mount.c:550): done
opening session (r
Package: clamav
Version: 0.94.dfsg.2-1lenny2
Severity: normal
Was using the option --exclude=//sys/ in clamscan to not scan the /sys
directory, when running a scan of the entire system (clamscan -r /). This
worked in clamscan 0.90.x and 0.92.1. After upgrade to lenny, my clamscan
report now
Package: release-notes
Version: 5.0.1
Severity: normal
http://wiki.debian.org/Etch2LennyUpgrade section "Backports" says:
If you do not use one of these exceptions, you can safely upgrade to lenny.
If you use one of these exceptions, set the pin-priority (see man
apt_preferences) tempor
Package: centericq
Version: 4.20.0-1
Severity: important
if a jabber message sent by an advanced client (e.g. psi) contains extra
-tags besides the content (e.g. for composing), centericq doesn't correctly
detect the fact that the message is encrypted, and doesn't decrypt it (losing
the message's
17 matches
Mail list logo
