*** This bug is a duplicate of bug 153996 ***
https://bugs.launchpad.net/bugs/153996
I'll make this a dupe of bug 153996 (which seems better for a meta-bug).
This affects subversion (with --fs-type bdb), too.
** Changed in: db4.4 (Ubuntu)
Assignee: dAniel hAhler (blueyed) => (unassigned)
My system runs stable since 2007-10-02 (after replacing Ubuntu's
libdb4.4 package with Debian's 4.4.20-10). I am really disappointed that
nobody at Canonical Ltd. feels responsible for this bug. I mean - I've
installed the Gutsy server version and postfix/postgrey is not an exotic
combination, is i
** Changed in: db4.4 (Ubuntu)
Assignee: (unassigned) => dAniel hAhler (blueyed)
Status: New => In Progress
--
postgrey fails regularly : "fatal: Can't call method "txn_commit" on an
undefined value at /usr/sbin/postgrey line 223."
https://bugs.launchpad.net/bugs/135038
You received t
Installed the updated libdb4.4 package from debian/lenny. Fixes the
problem (no more mails from my cronscript). Can we expect an updated
package from Ubuntu any time soon?
(People following this 'advise': at your risk off course)
--
postgrey fails regularly : "fatal: Can't call method "txn_commi
Same with me. Brand new installed and updated Gutsy.
Implemented the "Cron Fix" described above.
--
postgrey fails regularly : "fatal: Can't call method "txn_commit" on an
undefined value at /usr/sbin/postgrey line 223."
https://bugs.launchpad.net/bugs/135038
You received this bug notification
I'm me-tooing this bug to get updates.
--
postgrey fails regularly : "fatal: Can't call method "txn_commit" on an
undefined value at /usr/sbin/postgrey line 223."
https://bugs.launchpad.net/bugs/135038
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug c
Same for me, and running Gutsy as well...
I was wondering why my email server stops to send emails once per day almost...
and now i discovered this bug report.. which is the same problem happening to
me... and since I've upgraded to gutsy... with feisty, zero problems.
--
postgrey fails regular
** Changed in: db4.4 (Debian)
Status: Unknown => Fix Released
--
postgrey fails regularly : "fatal: Can't call method "txn_commit" on an
undefined value at /usr/sbin/postgrey line 223."
https://bugs.launchpad.net/bugs/135038
You received this bug notification because you are a member of U
My postgrey dies 4 times each night. a random minute of each 3am, 4am,
5am and 6am.
I've been running a cronjob every minute that restarts postgrey if its
down and mails me for half a week.
Machine is gutsy upgraded from feisty (and it was stable on feisty). I
have little time to investigate the
** Also affects: db4.4 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441152
Importance: Unknown
Status: Unknown
--
postgrey fails regularly : "fatal: Can't call method "txn_commit" on an
undefined value at /usr/sbin/postgrey line 223."
https://bugs.launchpad.net/bugs
** Changed in: db4.4 (Ubuntu)
Importance: Undecided => Medium
--
postgrey fails regularly : "fatal: Can't call method "txn_commit" on an
undefined value at /usr/sbin/postgrey line 223."
https://bugs.launchpad.net/bugs/135038
You received this bug notification because you are a member of Ubunt
Ironically enough, my reading of the Debian bug is that postrgrey isn't
broken, it's libdb4.4. Adding libdb4.4 task.
** Changed in: postgrey (Ubuntu)
Importance: Medium => Undecided
Status: Confirmed => Invalid
** Also affects: db4.4 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: postgrey (Ubuntu)
Importance: Undecided => Medium
--
postgrey fails regularly : "fatal: Can't call method "txn_commit" on an
undefined value at /usr/sbin/postgrey line 223."
https://bugs.launchpad.net/bugs/135038
You received this bug notification because you are a member of Ub
I have to second Matt's remark that this is taking ages. This is a imho
a critical bug since it brings down the server's mail delivery
completely and regularly, yet has been open for 2 months now.
Is Daniel Mueller's suggestion of updating libdb4.4 working? If so,
please release it.
Regards, Mart
Why is it taking so long to get a response on this? postgrey is very
much broken in gutsy, and Debian already addressed the problem.
--
postgrey fails regularly : "fatal: Can't call method "txn_commit" on an
undefined value at /usr/sbin/postgrey line 223."
https://bugs.launchpad.net/bugs/135038
** Changed in: postgrey (Ubuntu)
Status: New => Confirmed
--
postgrey fails regularly : "fatal: Can't call method "txn_commit" on an
undefined value at /usr/sbin/postgrey line 223."
https://bugs.launchpad.net/bugs/135038
You received this bug notification because you are a member of Ubunt
With libdb4.4 version 4.4.20-10 from debian 'unstable' postgrey is
working stable for two days now.
Oct 4 02:15:55 x postgrey[x]: cleaning up old logs...
Oct 4 02:15:55 x postgrey[x]: cleaning up old entries...
Oct 4 02:15:55 x postgrey[x]: cleaning main database finished. before: x,
after:
Hi,
yesterday I have installed debian's libdb4.4 version 4.4.20-10 from the
'unstable' branch [1]. I read the debian bugtracker and found out that
they have raised a ticket[2] against postgrey as well. Let's hope that
the updated library solves the nightly postgrey-crash. I will report my
results
I just installed monit and turned monitoring postfix and postgrey,
because it takes down postfix. I agree this needs to be fixed for this
reason alone.
--
postgrey fails regularly : "fatal: Can't call method "txn_commit" on an
undefined value at /usr/sbin/postgrey line 223."
https://bugs.launchp
Thanks for your input guys. I think the importance needs raising on this
bug.
Very lame-ass workaround:
*/2 * * * * sleep 10; pidof postgrey >/dev/null || /etc/init.d/postgrey start
--
postgrey fails regularly : "fatal: Can't call method "txn_commit" on an
undefined value at /usr/sbin/postgrey
Just wanted to say I am seeing this same error at postgrey 1.27, gutsy.
Oct 2 02:53:16 bluejay postgrey[4121]: fatal: Can't call method
"txn_commit" on an undefined value at /usr/sbin/postgrey line 223.
--
postgrey fails regularly : "fatal: Can't call method "txn_commit" on an
undefined value
Hmm, the same error with the newest version of postgrey:
Oct 2 02:11:32 x postgrey[x]: cleaning up old logs...
Oct 2 02:11:32 x postgrey[x]: cleaning up old entries...
Oct 2 02:11:32 x postgrey[x]: cleaning main database finished. before: x,
after: x
Oct 2 02:11:32 x postgrey[x]: FATAL: Ca
I can confirm this behavior. It appears on my (brand-new!) Ubuntu
"gutsy" server as well. (The server struggles with about 10 SMTP
connections per minute). Every night between 1:00am and 7:00am postgrey
dies:
Oct 1 02:44:04 x postgrey[x]: cleaning up old logs...
Oct 1 02:44:04 x
23 matches
Mail list logo
