===
Von: Rupert Germann
An: Martin Sebald
Datum: Dienstag, 12. Dezember 2006, 10:34:17 [GMT +0100]
Betreff: Re: Error 500 when trying to edit tt_news entry
===8<==Original message text===
hi Martin,
I also tried it with PHP 5.2.0-7 on Debian and after I wasted some
Sorry... Forgot CC... ;-)
===8<===This is a forwarded message
Von: Martin Sebald <[EMAIL PROTECTED]>
An: sean finney <[EMAIL PROTECTED]>
Datum: Mittwoch, 21. März 2007, 22:26:00 [GMT +0100]
Betreff: Re: Bug#414456: [php-maint] Bug#414456: Ref. t
t;
script which gets live interpreted by PHP when clicking through the page.
===8<===This is a forwarded message====
Von: Rupert Germann
An: Martin Sebald
Datum: Dienstag, 12. Dezember 2006, 10:34:17 [GMT +0100]
Betreff: Re: Error 500 when trying to edit tt_news entry
===8<
Hi Sean!
>> PS: tt_news is not a binary extension. Sean asked me. It's just
>> a "normal" script which gets live interpreted by PHP when clicking
>> through the page.
> okay, that's good news, actually, since it means there's more likely
> something we can do about it.
Great. ;-)
> now, you ment
Hello Sean!
>> Well, the only thing the server shows are these two lines:
>> [Fri Dec 08 14:17:08 2006] [error] [client 84.162.86.223] (104)Connection
>> reset by peer: FastCGI: comm with server
>> "/var/www/php-fcgi-scripts/www.domain.tld/php-fcgi-starter" aborted: read
>> failed, referer:
>> h
Hello Sean!
> after a bit of time, i've got typo3 installed and the tt_news extension
> loaded. however, i can't seem to find my way to whatever part of the
> menu/procedure you're talking about in the original bug report. could
> you give some detailed step-by-step instructions for someone who'
Hi Sean, Hi Jean-Luc,
first of all thank you for your support Jean-Luc. :-)
> i've made a tentative new version of php available at:
> http://people.debian.org/~seanius/php5/sid/
Unfortunally the only package I can use is php5_5.2.0-11_all.deb , all
other packages are for amd64 only. php5_5.2.0-
Hello Sean,
now after Etch is released how about a fancy little PHP 5.2.1 package? :-P
The bug is still there and a big problem for me. i really hope 5.2.1 will
fix this how Rupert told me.
Regards,
Martin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble
Package: libapache2-mod-auth-mysql
Version: 4.3.9-2
Hello,
I'm experiencing strange problems with libapache2-mod-auth-mysql. I
personally experienced it only on one virtual host with Typo3 installed.
But this may has nothing to say, maybe my customers did not complain yet.
Here's what I get from
Package: libapache2-mod-auth-mysql
Version: 4.3.9-2.1+b1
Hello,
because I was experiencing problems with libapache2-mod-auth-mysql 4.3.9-2
(see other bug I submitted today) I upgraded to 4.3.9-2.1+b1. But this
version seems to be a complete showstopper for me. I do not get anything
from the webse
Package: clamav-freshclam
Version: 0.88.4-1
Hello,
after upgrading from 0.88.3-1 to 0.88.4-1 I experience the following
problem when trying to start clamav-freshclam:
> /etc/init.d/clamav-freshclam restart
> Starting ClamAV virus database updater: freshclam/sbin/start-stop-daemon:
> stat /var/r
Hello Matthew!
>> I'm experiencing strange problems with libapache2-mod-auth-mysql. I
>> personally experienced it only on one virtual host with Typo3 installed.
>> But this may has nothing to say, maybe my customers did not complain
>> yet. Here's what I get from the Apache2 error.log:
>>> [Wed
Hello Matthew!
> Check (using ldd or apt-cache show) that anything that might link against
> both Apache and MySQL (directly *or* indirectly) is using the same
> libmysqlclient version. Fixing it is extra special, but in this case I'd
> suggest just going back to 4.3.9-2. -2.1 was a transition u
Hello Matthew!
>>> Very strange, though. If you turn the log level in Apache down to
>>> debug, you should get a pretty comprehensive trace of what's being
>>> done; that info might help pinpoint the cause of the trouble.
>> I'll do that and click through the Typo3 backend and hope that the erro
Hello Matthew!
>> Very strange, though. If you turn the log level in Apache down to
>> debug, you should get a pretty comprehensive trace of what's being done;
>> that info might help pinpoint the cause of the trouble.
> I'll do that and click through the Typo3 backend and hope that the error
>
Hello Matthew!
>> Talking again about the bug here: It is really hard to find and only
>> appears _sometimes_ and when clicking through the backend of Typo3.
> This intermittency is very weird, and the application-specificity worries
> me too. You're saying that if you put the exact same Apache
Package: nagios-mysql
Version: 1.4-2
Hello,
when upgrading Nagios to version 1.4-2 I experienced the following:
> Setting up nagios-mysql (1.4-2) ...
> dpkg: error processing nagios-mysql (--configure):
> subprocess post-installation script returned error exit status 10
> Errors were encountere
Package: bind
Version: 1:9.9.3.dfsg.P2-4
Hello,
please include support for BIND9 Response Rate Limiting (RRL) into Debian
package of BIND9.
See:
https://www.isc.org/blogs/isc-adds-ddos-defense-module-to-bind-software/
http://ss.vix.su/~vjs/rrlrpz.html
http://www.redbarn.org/dns/ratelimits
Reaso
Hello all,
problem solved!
We had only 10 ports defined as passive ports. Every client needs two
passive ports. This is the reason why pure-ftpd set a 5 user maximum limit.
See here:
http://www.howtoforge.com/forums/showthread.php?t=52838
Maybe this should somehow documented?
Cheers,
Martin
Package: duplicity
Version: 0.6.18-6
Hello all,
because of the ssh/scp issues and a lot of other fixed bugs I would like to
request an upgrade to latest version of duplicity, at the moment: 0.6.20.
I cannot do any backups to scp/ssh target with 0.6.18 or 0.6.17 and still
have to use 0.6.15, whic
Package: pure-ftpd
Version: 1.0.36-1.1
Severity: important
Hello all,
my customers are complaining that they cannot use FTP server here and get
this message:
> 421 5 users (the maximum) are already logged in, sorry
This is strange because I set the maximum users to 50 (which is also the
default
Package: duply
Version: 1.5.5.1-2
Hello,
after upgrading from 1.5.4 to 1.5.5 passwords are no longer accepted. If
you run the script it shows a password input field - which makes absolutly
no sense for automatic scripts. ;-) On my machines I use FTP and SCP for
backup, both methods have the same
Hi,
is there any development for this bug? It's almost three months since I
posted about the problem - which is a very serious one in my eyes. On a
medium populated server 5 concurrent users are just nothing.
Cheers,
Martin
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Hi Hilmar,
sorry, that was more than 6 years ago. I switched to pure-ftpd many years ago.
I even did not remember the problem or if I switched because of that. So I
cannot be any help anymore. Sorry.
Cheers,
Martin
Package: sasl2-bin
Version: 2.1.26.dfsg1-11
Severity: important
Hi,
the saslauthd fails here on our mail server for weeks now. It seems that after
a certain amount of login (successful and tries) a limit is reached and the
daemon silently (!) fails - people cannot log into SASL-Auth anymore.
I s
Hello Dan,
thank you for the reply. Here you are:
/etc/default/saslauthd:
START=yes
DESC="SASL Authentication Daemon"
NAME="saslauthd"
MECHANISMS="pam"
MECH_OPTIONS=""
#THREADS=5
THREADS=0
OPTIONS="-r -c -m /var/spool/postfix/var/run/saslauthd"
(I just changed threads from 5 to 0, thank you for
Hello Dan,
here you go:
/etc/postfix/sasl/smtpd.conf
pwcheck_method: saslauthd
mech_list: plain login
allow_plaintext: true
auxprop_plugin: sql
sql_engine: mysql
sql_hostnames: 127.0.0.1
sql_user: xxx
sql_passwd: xxx
sql_database: xxx
sql_select: select password from mail_user where email = '%u@%
Hello Dan,
outch, this did not work. I just noticed that the server was completly out of
resources. I checked and found hundrets or better even thousands of saslauthd
threads. I had to pkill these tasks, now the server is recovering.
I put THREADS=5 back into config and restart saslauthd every ho
Package: composer
Version: 1.2.1-1
Hello,
can you fix these issues?
http://debomatic-amd64.debian.net/distribution#jessie-backports/composer/1.2.1-1~bpo8+1/buildlog
I would really like to see this package in jessie-backports.
Cheers,
Martin
Package: monit
Version: 5.18-1~bpo8+1
Hello,
I'm experiencing a bug in jessie-backports monit version 5.18-1~bpo8+1:
/etc/monit/conf.d/memcached:8: Cannot activate service check. The process
status engine was disabled.
It looks like this bug:
https://bitbucket.org/tildeslash/monit/issues/379/e
Hello Sergey,
thank you very much! I will test it, as soon as it is available in the
jessie-backports repository. Where it is not available, yet, unfortunally.
Cheers,
Martin
Hello Sergey,
sorry, I did not know that I have to build the package from the dsc file myself.
I just built the package and installed it. This time I was able to start Monit
with my config file.
The bug is fixed. Thank you! :-)
Cheers,
Martin
Hi Stefan!
> The init script of the versions up to 2.2.3-4 had this problem. Maybe
> you have modified your init script and not upgraded it?
> Does /etc/init.d/apache.dpkg-dist exist?
No, I did not modify the init script. Also there is no
/etc/init.d/apache2.dpkg-dist on my server. /etc/init.d/ap
Hello all,
unfortunally the DefaultMinClassProcessCount workaround has no effect here.
I'm using 2.2-1 of libapache2-mod-fcgid with Apache 2.2.8.
I also tried to set things inside the VHost as described here:
http://jay.vox.com/library/post/mod_fcgid-ignoring-fastcgi-config-settings.html
It did
Package: apache2-mpm-worker
Version: 2.2.8-1
Hi all,
when I or a script (like logrotate) tries to restart Apache2 with the
command "/etc/init.d/apache2 restart" it fails printing out the following:
> Restarting web server: apache2(98)Address already in use: make_sock: could
> not bind to addres
Hello all,
as the maintainer of Jabberserver jabber.hot-chilli.net I would also love
to see MySQL support for the Debian package of ejabberd.
If this is a better idea and makes more sense also in a seperate package
like ejabberd-mysql.
> But still, I don't need it, so I'm not going to be its ma
Package: php5
Version: 5.2.6-2
Severity: critical
Hello,
after upgrading from php5 5.2.5-3 to 5.2.6-2 we experienced the following
errors:
Wordpress:
> Fatal error: strftime() [function.strftime]:
> Timezone database is corrupt - this should *never* happen! in
> /var/www/www.domain.tld/wp-cont
Hello Sean!
>> Wordpress:
>>> Fatal error: strftime() [>> href='function.strftime'>function.strftime]: Timezone database is
>>> corrupt - this should *never* happen! in
>>> /var/www/www.domain.tld/wp-content/plugins/timezone.php on line 150
> oy. this definitely needs to be fixed then, as we're g
200 (CEST)]:
> On Wed, July 23, 2008 14:34, Martin Sebald wrote:
>> function option_gmt_offset() {
> I've tried to reproduce this with a PHP file containing just this function
> and a call "var_dump(option_gmt_offset())". Running that file with
> php5-cli just yield
Hello Sean,
well, we are using some kind of hybrid system. But basicly it is a system
based on the unstable tree, but I'm sure there are some stable packages
installed as well. The stable packages are replaced by unstable versions if
apt-get wants to. So some are left, but not many. And we are usi
Hello Sean, Hello Thijs!
> my guess is that your security rules are blocking access to
> /etc/localtime and files under /usr/share/zoneinfo then.
Yes, that was it!
I unblocked these files/directories and everything works fine now! :-)
Maybe this information should be put somewhere for other sec
Hello all,
I think that the following Postfix problem is related to this bug. I found
several entries in newsgroups linking to this bug report page.
Jan 19 16:12:55 mailserver postfix/smtp[13270]: setting up TLS connection to
mail.domain.tld
Jan 19 16:12:55 mailserver postfix/smtp[13270]: SSL_co
Hello Kurt,
will/could the changes in 0.9.8a-7 have any effect on the postfix issues
I'm experiencing? Is it worth a try?
If you need any detailed information about the postfix configuration I'm
running I will be happy to hand it over to you.
Regards,
Martin
--
To UNSUBSCRIBE, email to [EMAI
Hello Kurt,
>> will/could the changes in 0.9.8a-7 have any effect on the postfix issues
>> I'm experiencing? Is it worth a try?
> A new postfix version has been uploaded to unstable, which has as
> changelog entry:
> * New upstream, fixes various TLS/SASL bugs.
> I suggest you try that.
Thank yo
Hello again,
I'm sorry, but looking into the logs the last days and trying a few thing I
have to say the following:
The Postfix bugs are still there, either without the special
smtpd_tls_cipherlist parameter from Yari and with this parameter.
Without I get some the following errors in mail.log:
Package: proftpd
Version: 1.3.0-2
Hello,
when trying to start ProFTPd I noticed that /etc/proftpd/modules.conf is
not parsed:
> Starting ftp server: proftpd - Fatal: unknown configuration directive
> 'SQLConnectInfo' on line 112 of '/etc/proftpd/proftpd.conf'
> failed!
After adding content of
Package: proftpd
Version: 1.3.0-2
Hello,
when starting ProFTPd 1.3.0-2 I get the following output on the console:
> Starting ftp server: proftpd - IPv6 getaddrinfo 'servername.domain.tld'
> error: Name or service not known
The daemon runs and works as it should but according to Google the pack
Package: proftpd
Version: 1.3.0-2
Hello,
when installing proftpd 1.3.0-2 the following output appears on the
console:
> Setting up proftpd (1.3.0-2) ...
> Adding system user `proftpd'...
> Adding new user `proftpd' (115) with group `nogroup'.
> configuration error - unknown item 'FAIL_DELAY' (n
Hello!
> We believe that the bug you reported is fixed in the latest version of
> openssl, which is due to be installed in the Debian FTP archive:
Was this meant for me? Otherwise sorry for spamming around... ;-)
I upgraded to openssl 0.9.8a-6 but the Postfix errors stayed.
I also got a mail f
Hello!
>> We believe that the bug you reported is fixed in the latest version of
>> openssl, which is due to be installed in the Debian FTP archive:
> I upgraded to openssl 0.9.8a-6 but the Postfix errors stayed.
It works now. I only upgraded openssl and forgot to upgrade libssl0.9.8.
After upg
Package: ejabberd
Version: 2.1.3-2
Hello Konstantin and Gerfried,
as there again are many bugfixes in ejabberd 2.1.4 (released June 4th 2010)
I wanted to take the opportunity to ask you if there will be a Debian
package for this version. :-)
Kindest regards,
Martin
--
To UNSUBSCRIBE, email t
Package: ejabberd
Version: 2.1.3-2
Hello,
this was already brought up in bug #507144
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507144
which is closed and supposed to be fixed in version 2.1.0-1.
But there still isn't any mysql driver in the package.
Was this wish rejected or is it still
Hello,
I want to support this wish, because 2.1.6 brings some interesting
features, first of all captcha support. Here's the list from ejabberd
website:
* BOSH: Fix rare loop, support vhosts, allow module restart
* Config: Default configuration allows registrations only from localhost
* Config: S
Package: proftpd-basic
Version: 1.3.3a-1
Hello all,
I'm using ProFTPd with MySQL, no other modules.
When trying to transfer a file with 1.3.3a-1 the client gets disconnected
after sending the file (sent file seems to be ok). With cmdline client the
connection just breaks, other clients (like Tot
Hello Francesco,
sure, here is the configuration. Note that I run this configuration on
three servers - all had the problem. After downgrading and without altering
the configuration it worked again.
Regards,
Martin
-
proftpd.co
Package: php5-cgi
Version: 5.3.2-1
Hello all,
I experienced a lot of segfaults in syslog with php5-cgi 5.3.2-1, like
these error messages:
> Apr 14 16:24:12 oberon kernel: [144632.380067] php5-cgi[7051]: segfault at 13
> ip 082fbb77 sp bfe25a30 error 4 in php5-cgi[8048000+6a7000]
> Apr 14 16:24
Hello Sean!
> * what requests are generating the segfaults (you should be able to trace
> the 500 errors to the URL's in question)
Well, I don't see much Apache logs. Just stuff like:
> [warn] (104)Connection reset by peer: mod_fcgid: read data from fastcgi
> server error.
> [error] [client xx.
Package: ejabberd
Version: 2.1.3-1
Hello all,
after logrotate ejabberd logs to ejabberd.log.1, ejabberd.log remains as a
file with 0 bytes size.
What happens the day after (when ejabberd.log.1 gets compressed to
ejabberd.log.2.gz) I don't know. Haven't reached this point yet.
Regards,
Martin
Package: libmail-dkim-perl
Version: 0.32-1
Hello Magnus,
could you please regard upgrading to version 0.33? There is a bug in
Mail::DKIM 0.32 or earlier.
From release notes:
> (btw, if testkeys fails and you believe your DNS is correctly serving
> your DKIM public keys, you may need to upgrade
Hello all,
I am experiencing the same problem as described here with apache2 version
2.4.38-3+deb10u3 (buster) and also version 2.4.43-1~bpo10+1 (buster-backports).
The proxy modules are loaded but I cannot proxy WebSocket with Apache2. Here's
some more information:
"apache2ctl -M | grep proxy"
60 matches
Mail list logo
