Bug#670636: Multiple security issues in April security release
What about Debian Squeeze? Are you planning to provide fixed mysql packages for the current stable release of Debian, too? Thanks. -- Mit freundlichen Gruessen / Kind regards, Thomas Babut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670438: Multiple serious crashes after updating to MySQL 5.1.61-0+squeeze1
*, unsigned int, bool*)+0x2a4) [0x7f7b80dcf584] Apr 24 15:18:46 euros mysqld: /usr/sbin/mysqld(open_and_lock_tables_derived(THD*, TABLE_LIST*, bool)+0x5c) [0x7f7b80dd50ec] Apr 24 15:18:46 euros mysqld: /usr/sbin/mysqld(mysql_insert(THD*, TABLE_LIST*, ListItem, ListListItem , ListItem, ListItem, enum_duplicates, bool)+0xd3) [0x7f7b80e0a7b3] Apr 24 15:18:46 euros mysqld: /usr/sbin/mysqld(mysql_execute_command(THD*)+0xbd9) [0x7f7b80d93e99] Apr 24 15:18:46 euros mysqld: /usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x3fb) [0x7f7b80d98dbb] Apr 24 15:18:46 euros mysqld: /usr/sbin/mysqld(Query_log_event::do_apply_event(Relay_log_info const*, char const*, unsigned int)+0x41c) [0x7f7b80e4c27c] Apr 24 15:18:46 euros mysqld: /usr/sbin/mysqld(apply_event_and_update_pos(Log_event*, THD*, Relay_log_info*)+0xfd) [0x7f7b80ecb9dd] Apr 24 15:18:46 euros mysqld: /usr/sbin/mysqld(handle_slave_sql+0x81b) [0x7f7b80ecd23b] Apr 24 15:18:46 euros mysqld: /lib/libpthread.so.0(+0x68ca) [0x7f7b805d98ca] Apr 24 15:18:46 euros mysqld: /lib/libc.so.6(clone+0x6d) [0x7f7b7f12192d] Apr 24 15:18:46 euros mysqld: Apr 24 15:18:46 euros mysqld: Trying to get some variables. Apr 24 15:18:46 euros mysqld: Some pointers may be invalid and cause the dump to abort. Apr 24 15:18:46 euros mysqld: Query (7f773c020385): is an invalid pointer Apr 24 15:18:46 euros mysqld: Connection ID (thread ID): 20 Apr 24 15:18:46 euros mysqld: Status: NOT_KILLED === -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mysql-server-5.1 depends on: ii adduser 3.112+nmu2 add and remove users and groups ii debconf [de 1.5.36.1 Debian configuration management sy ii libc6 2.11.3-2 Embedded GNU C Library: Shared lib ii libdbi-perl 1.612-1 Perl Database Interface (DBI) ii libgcc1 1:4.4.5-8GCC support library ii libmysqlcli 5.1.61-0+squeeze1MySQL database client library ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip ii mysql-clien 5.1.61-0+squeeze1MySQL database client binaries ii mysql-commo 5.1.61-0+squeeze1MySQL database common files, e.g. ii mysql-serve 5.1.61-0+squeeze1MySQL database server binaries ii passwd 1:4.1.4.2+svn3283-2+squeeze1 change and administer password and ii perl5.10.1-17squeeze3Larry Wall's Practical Extraction ii psmisc 22.11-1 utilities that use the proc file s ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages mysql-server-5.1 recommends: ii bsd-mailx [mailx] 8.1.2-0.20100314cvs-1 simple mail user agent ii heirloom-mailx [ma 12.4-2feature-rich BSD mail(1) ii libhtml-template-p 2.9-2 module for using HTML Templates wi Versions of packages mysql-server-5.1 suggests: pn tinycanone (no description available) -- Configuration Files: /etc/logcheck/ignore.d.paranoid/mysql-server-5_1 [Errno 13] Keine Berechtigung: u'/etc/logcheck/ignore.d.paranoid/mysql-server-5_1' /etc/logcheck/ignore.d.server/mysql-server-5_1 [Errno 13] Keine Berechtigung: u'/etc/logcheck/ignore.d.server/mysql-server-5_1' /etc/logcheck/ignore.d.workstation/mysql-server-5_1 [Errno 13] Keine Berechtigung: u'/etc/logcheck/ignore.d.workstation/mysql-server-5_1' -- debconf information: mysql-server/error_setting_password: mysql-server-5.1/nis_warning: mysql-server-5.1/really_downgrade: false mysql-server-5.1/start_on_boot: true mysql-server-5.1/postrm_remove_databases: false mysql-server/password_mismatch: mysql-server/no_upgrade_when_using_ndb: -- Mit freundlichen Gruessen / Kind regards, Thomas Babut -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#463793: Inconsistent with sysklogd
Hello, we have noticed on a new installation, too, that the restart messages from rsyslog are not being ignored by logcheck. Martin, you said that logcheck has the policy not to ignore restart messages, but even in Lenny there is a regular expression to ignore restart messages from sysklogd. There should be made a consistent policy or decision. Otherwise there should be a way to ignore the restart from rsyslog on logrotate, because this is no error or malfunction. -- Mit freundlichen Gruessen / Kind regards, Thomas Babut -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495917: Fixed in upstream
Hi everyone, we have the same problem with our Juniper Firewalls. I have created a case do get the patch from Juniper, too. Another workaround is to patch the openssh-client. In the CVS-Upstream of OpenSSH 5.1 this has been already fixed about 2 months ago: http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/ssh.c.diff?r1=1.318;r2=1.319 Perhaps this patch should be included also in the debian package. Thanks. -- Mit freundlichen Gruessen / Kind regards, Thomas Babut -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491522: The same here
Hi, I've got the same problem since the update to 2.6.25-2-686 kernel. My lenny system worked fine with the older 2.6.24 kernel. Since the new kernel upstream version my machine freezed sporadically after some uptime 3 times now. There are no kernel messages before this happens. Unfortunately I purged the older kernel after the update. -- Mit freundlichen Gruessen / Kind regards, Thomas Babut [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] / GPG: 0x9EA93CB2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491522: Additional information
Some more information about my machine in the attachments... Thanks in advance. -- Mit freundlichen Gruessen / Kind regards, Thomas Babut [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] / GPG: 0x9EA93CB2 # dmidecode 2.9 SMBIOS 2.4 present. 22 structures occupying 1128 bytes. Table at 0x000FBC40. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: P1.30 Release Date: 09/04/2006 Address: 0xF Runtime Size: 64 kB ROM Size: 512 kB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25/1.2 MB floppy services are supported (int 13h) 3.5/720 KB floppy services are supported (int 13h) 3.5/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported LS-120 boot is supported ATAPI Zip drive boot is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported BIOS Revision: 8.12 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: To Be Filled By O.E.M. Product Name: 775i945GZ Version: To Be Filled By O.E.M. Serial Number: To Be Filled By O.E.M. UUID: 00020003-0004-0005-0006-000700080009 Wake-up Type: Power Switch SKU Number: To Be Filled By O.E.M. Family: To Be Filled By O.E.M. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Product Name: 775i945GZ Version: Serial Number: Asset Tag: Features: Board is a hosting board Board is replaceable Location In Chassis: Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 21 bytes Chassis Information Manufacturer: To Be Filled By O.E.M. Type: Desktop Lock: Not Present Version: To Be Filled By O.E.M. Serial Number: To Be Filled By O.E.M. Asset Tag: To Be Filled By O.E.M. Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 Handle 0x0004, DMI type 4, 35 bytes Processor Information Socket Designation: CPUSocket Type: Central Processor Family: Pentium 4 Manufacturer: Intel ID: 65 0F 00 00 FF FB EB BF Signature: Type 0, Family 15, Model 6, Stepping 5 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Hyper-threading technology) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel(R) Pentium(R) D CPU 3.20GHz Voltage: 1.3 V External Clock: 200 MHz Max Speed: 3200 MHz Current Speed: 3200 MHz Status: Populated, Enabled Upgrade: Other
Bug#403721: Joomla crashes MySQL-Server
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm running Debian Etch AMD64-Port on an AMD64-System with all newest updates: ii mysql-client-5.0 5.0.32-3 mysql database client binaries ii mysql-common 5.0.32-3 mysql database common files (e.g. /etc/mysql ii mysql-server-5.0 5.0.32-3 mysql database server binaries Newest CMS Joomla 1.0.12 is installed. And when you click on the category manager in Joomla, the following mysql query is crashing the server: DB function failed with error number 2013 Lost connection to MySQL server during query SQL=SELECT c.*, c.checked_out as checked_out_contact_category, g.name AS groupname, u.name AS editor,COUNT( DISTINCT s2.checked_out ) AS checked_out , z.title AS section_name FROM jos_categories AS c LEFT JOIN jos_users AS u ON u.id = c.checked_out LEFT JOIN jos_groups AS g ON g.id = c.access LEFT JOIN `jos_content` AS s2 ON s2.catid = c.id AND s2.checked_out 0 LEFT JOIN jos_sections AS z ON z.id = c.section WHERE c.section NOT LIKE '%com_%' AND c.published != -2 GROUP BY c.id ORDER BY c.section, c.ordering, c.name LIMIT 30 On a 32-Bit-System this query works fine. And this only happens on the AMD64-System with the new mysql-server-5.0.32-3. With the earlier mysql version 5.0.30-3 Joomla works fine on the AMD64-System. So this is the same bug as reported here? Thanks. - -- Regards, Thomas Babut PGP ID: 9EA93CB2 E-Mail: [EMAIL PROTECTED] Jabber: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFzD6J+XUy4J6pPLIRAqv0AJ0UeB13x5qv+0mtKcnvLAorhwVGgACeMkET GCxW2VfBsskvZXjdE4eTWEs= =KTZH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399329: 3 security issues: PMASA-2006-7, PMASA-2006-8, PMASA-2006-9
Package: phpmyadmin Version: 4:2.9.0.3-1 Severity: critical Tags: security 3 security issues were fixed with the new version of phpMyAdmin 2.9.1.1. All 3 issues affects all previous versions of phpMyAdmin. This also applies to Sarge. See this security announcements: http://www.phpmyadmin.net/home_page/security.php?issue=PMASA-2006-7 http://www.phpmyadmin.net/home_page/security.php?issue=PMASA-2006-8 http://www.phpmyadmin.net/home_page/security.php?issue=PMASA-2006-9 -- Best regards, Thomas Babut E-Mail: [EMAIL PROTECTED] PGP ID: 9EA93CB2 Jabber: [EMAIL PROTECTED] signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#398817: This is strange
Hi again, currently I cannot provide any more information. The segmentation faults didn't happen any more after I have reported them. But I didn't change anything on the system either. :) I've also made some stress testing with ab2 with the same configuration and loglevel debug on another server and everything runs fine. So I have no idea, what the problem could have been. -- Best regards, Thomas Babut E-Mail: [EMAIL PROTECTED] PGP ID: 9EA93CB2 Jabber: [EMAIL PROTECTED] signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#398817: apache2/2.2.3-3.1 Segmentation faults (11)
Package: apache2.2-common Version: 2.2.3-3.1 Severity: grave Hi, on a Debian Testing system with some packages from Unstable (php5) I'm getting in apache2/2.2.3-3.1 many Segmentation faults (11) after the apache server is running for some hours. It's a frequently high visited webserver. The apache error logfile gives this: [Wed Nov 15 20:04:08 2006] [notice] child pid 32443 exit signal Segmentation fault (11) [Wed Nov 15 20:04:08 2006] [notice] child pid 2567 exit signal Segmentation fault (11) [Wed Nov 15 20:04:11 2006] [notice] child pid 435 exit signal Segmentation fault (11) [Wed Nov 15 20:04:11 2006] [notice] child pid 451 exit signal Segmentation fault (11) [Wed Nov 15 20:04:11 2006] [notice] child pid 2320 exit signal Segmentation fault (11) [Wed Nov 15 20:04:13 2006] [notice] child pid 2074 exit signal Segmentation fault (11) and so on... After restarting the apache server it's running fine again for some hours. Following related packages are installed: apache2-mpm-prefork 2.2.3-3.1 apache2-prefork-dev 2.2.3-3.1 apache2-utils 2.2.3-3.1 apache2.2-common 2.2.3-3.1 libapache2-mod-auth-plain 2.0.48-4-2.2 libapache2-mod-perl2 2.0.2-2.2 libapache2-mod-php5 5.2.0-3 libapache2-mod-python 3.2.10-2 libapache2-svn 1.4.0-5 libapr1 1.2.7-7 libapr1-dev 1.2.7-7 libaprutil1 1.2.7+dfsg-2 libaprutil1-dev 1.2.7+dfsg-2 libmysqlclient15-dev 5.0.26-3 libmysqlclient15off 5.0.26-3 linux-image-2.6.17-2-amd64 2.6.17-9 mysql-client-5.0 5.0.26-3 mysql-common 5.0.26-3 mysql-server 5.0.26-3 mysql-server-5.0 5.0.26-3 php5 5.2.0-3 php5-cgi 5.2.0-3 php5-cli 5.2.0-3 php5-common 5.2.0-3 php5-curl 5.2.0-3 php5-dev 5.2.0-3 php5-gd 5.2.0-3 php5-mcrypt 5.1.2-1-tomek1 (original sid source built against php5-5.2.0-3) php5-mhash 5.2.0-3 php5-mysql 5.2.0-3 php5-recode 5.2.0-3 php5-xmlrpc 5.2.0-3 php5-xsl 5.2.0-3 The following apache2 modules are enabled: actions alias auth_basic authn_file auth_plain authz_default authz_groupfile authz_host authz_user autoindex cgi dav_fs dav dav_svn dir env expires headers include info mime mime_magic negotiation perl php5 rewrite setenvif status I can provide more informations if needed. Personally I don't think it has to do something with one of the following bug reports: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=392189 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397904 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=392373 And because I don't know which package is causing the problem, I have created a new bug report instead of replying to another one. Thanks. -- Best regards, Thomas Babut E-Mail: [EMAIL PROTECTED] PGP ID: 9EA93CB2 Jabber: [EMAIL PROTECTED] signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#398800: Obviously duplicate of #398584
Hi, this is obviously a duplicate bug report of #398584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398584 -- Best regards, Thomas Babut E-Mail: [EMAIL PROTECTED] PGP ID: 9EA93CB2 Jabber: [EMAIL PROTECTED] signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#398584: php5-imap needs to be recompiled against PHP 5.2.0
Package: php5-imap severity: grave The package php5-imap is uninstallable in unstable, because of the new PHP 5.2.0 packages. Assuming, that PHP 5.2.0 gets soon in to testing, this problem also applies to testing, too. -- Best regards, Thomas Babut [EMAIL PROTECTED] signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#398587: php5-pspell needs to be recompiled against PHP 5.2.0
Package: php5-pspell severity: grave The package php5-pspell is uninstallable in unstable, because of the new PHP 5.2.0 packages. Assuming, that PHP 5.2.0 gets soon in to testing, this problem also applies to testing, too. -- Best regards, Thomas Babut [EMAIL PROTECTED] signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#398585: php5-imagick needs to be recompiled against PHP 5.2.0
Package: php5-imagick severity: grave The package php5-imagick is uninstallable in unstable, because of the new PHP 5.2.0 packages. Assuming, that PHP 5.2.0 gets soon in to testing, this problem also applies to testing, too. -- Best regards, Thomas Babut [EMAIL PROTECTED] signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#398026: php5-mcrypt needs to be recompiled against PHP 5.2.0
Package: php5-mcrypt severity: important The package php5-mcrypt is uninstallable in sid and testing, because of the new PHP 5.2.0 packages. This also applies to the packages php5-imap, php5-pspell, php5-imagick. -- Best regards, Thomas Babut [EMAIL PROTECTED] signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#396766: Would be great to have PHP 5.2 in Etch
Hi, PHP 5.2.0 brings many interesting performance and security improvements, so it would be great to have this new stable series in Debian Etch. Also PHP 5.1 is now officially obsolete, so it will propably not get any bug or security fixes from the PHP team. Thanks. -- Best regards, Thomas Babut [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#396638: PMASA-2006-6: XSS vulnerability
Package: phpmyadmin Version: 4:2.9.0.2-1 Severity: critical Tags: security A XSS vulnerability has been fixed in phpMyAdmin 2.9.0.3. All versions from 2.6.4 to 2.9.0.2 are affected. See this phpMyAdmin security announcement PMASA-2006-6 for more details: http://www.phpmyadmin.net/home_page/security.php?issue=PMASA-2006-6 -- Best regards, Thomas Babut [EMAIL PROTECTED] signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Bug#380060: Still no updated package?
Hi, is this package becoming unmaintained or why this bug doesn't get fixed after this report has been made 88 days ago? Thanks. -- Best regards, Thomas Babut [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383596: PHP 5.1.5 fixes multiple security flaws
Package: php5 Tags: security With the release of PHP 5.1.5 multiple security problems were fixed. The official announcement: http://www.php.net/release_5_1_5.php -- Best regards, Thomas Babut [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#366109: php5: PHP 5.1.3, 5.1.4 released
Hi, why there are still no updated packages available? PHP 5.1.4 has been released now for about 4 weeks with some important security fixes. -- Best regards, Thomas Babut [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#352468: Server crashing with MySQL 5.0.22 but not with 5.0.20
Hi, last night I've upgraded on a Debian Etch Server the MySQL-Server from 4.1 to 5.0.22. After this the MySQL-Server started to crash regulary. The installed architecture is AMD64. In the MySQL-Error-Log I find this: --- 060603 10:25:40 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 060603 10:25:40 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 0 210480. InnoDB: Doing recovery: scanned up to log sequence number 0 210480 060603 10:25:40 InnoDB: Started; log sequence number 0 210480 060603 10:25:40 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.22-Debian_1-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian Etch distribution mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=134217728 read_buffer_size=1044480 max_used_connections=1 max_connections=500 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1665068 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. --- Then I downgraded the MySQL-Server from 5.0.22 to 5.0.20 and the Server seems now running fine. What bug or problem this could be? Thanks. -- Best regards, Thomas Babut [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#352468: Server crashing with MySQL 5.0.22 but not with 5.0.20, #2
Hi again, I think this is exactly the problem: http://www.vbulletin.com/forum/bugs35.php?do=viewbugid=2449 They say it's a mysql bug and will be probably fixed in 5.0.23. -- Best regards, Thomas Babut [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#291392: Very poor performance of unserialize() function in PHP 4.3.10
Package: php4 Version: 4.3.10-2 Since PHP 4.3.10 the function unserialize() has a big performance problem, as reported here: http://bugs.php.net/bug.php?id=31332 I've rebuilded a new PHP4-4.3.10 package on Debian Sarge from the newest CVS-Version and it works fine now, like in 4.3.9 and earlier. I don't know whether a single patch exists to fix this problem or not. Regards, Thomas Babut -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
