[Bug 167354] Review Request: amavisd-new
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: amavisd-new
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167354
------- Additional Comments From paul(a)xtdnet.nl 2006-01-24 22:11 EST -------
I'm still trying to debug this and get amavisd-new running. Looking a bit
further into my db error, I noticed:
["DBI:SQLite:dbname=$MYHOME/sql/mail_prefs.sqlite", '', ''] );
Howeverm there is no 'sql' directory included with amavisd-new in the rpm.
Perhaps either the sqlite depedancy needs to be dropped, or this file needs to
be included?
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
17 years, 10 months
[Bug 177788] New: Directory for pid-file for spamassassin is not included in spamassassin package
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177788
Summary: Directory for pid-file for spamassassin is not included
in spamassassin package
Product: Fedora Core
Version: devel
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: normal
Component: spamassassin
AssignedTo: wtogami(a)redhat.com
ReportedBy: rmo(a)sunnmore.net
CC: fedora-perl-devel-
list@redhat.com,felicity@kluge.net,jm(a)jmason.org,parkerm
@pobox.com,reg+redhat@sidney.com,wtogami(a)redhat.com
Description of problem:
Directory for pid-file for spamassassin is not included in spamassassin package.
/var/run/spamassassin/ should be included in spec-file
Version-Release number of selected component (if applicable):
spamassassin-3.1.0-3.fc5.1 (installed on FC4 server)
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
17 years, 10 months
[Bug 167354] Review Request: amavisd-new
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: amavisd-new
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167354
------- Additional Comments From paul(a)xtdnet.nl 2006-01-20 14:03 EST -------
I used the first rpm you put up, had that error and then found your latest rpm,
and did a rpm -U.
An strace ends with problems for BDB and "Destroy". But I did install the FE
BerkeleyDB rpm as well.
My guess was this could be some missing perl dependancy, but I cannot figure out
the package that would be missing.
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
17 years, 10 months
[Bug 167354] Review Request: amavisd-new
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: amavisd-new
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167354
paul(a)xtdnet.nl changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |paul(a)xtdnet.nl
------- Additional Comments From paul(a)xtdnet.nl 2006-01-20 01:54 EST -------
when updating from your first to your last rpm, I noticed amavisd is restarted
twice:
[root@cdc ~]# rpm -Uhv /usr/src/redhat/RPMS/noarch/amavisd-new-2.3.3-4.noarch.rpm
Preparing... ########################################### [100%]
1:amavisd-new warning: /etc/amavisd/amavisd.conf created as
/etc/amavisd/amavisd.conf.rpmnew
########################################### [100%]
Shutting down amavisd: Can't SIGTERM amavisd[1337]: No such process at
/usr/sbin/amavisd line 8983., can't stop the process
[FAILED]
Starting amavisd: Pid_file "/var/run/amavisd/amavisd.pid" already exists.
Overwriting!
[ OK ]
Stopping clamd.amavisd: [ OK ]
Starting clamd.amavisd: [ OK ]
[root@cdc ~]#
More importantly, amavisd never starts for me. It goes through a lot of good
messages and then ends with an error:
Jan 20 01:54:19 cdc amavis[1588]: Found decoder for .zoo at /usr/bin/zoo
Jan 20 01:54:19 cdc amavis[1588]: Found decoder for .lha at /usr/bin/lha
Jan 20 01:54:19 cdc amavis[1588]: Found decoder for .cab at /usr/bin/cabextract
Jan 20 01:54:19 cdc amavis[1588]: No decoder for .tnef tried: tnef
Jan 20 01:54:19 cdc amavis[1588]: Internal decoder for .tnef
Jan 20 01:54:19 cdc amavis[1588]: Found decoder for .exe at /usr/bin/unrar;
/usr/bin/lha; /usr/bin/unarj
Jan 20 01:54:19 cdc amavis[1588]: Using internal av scanner code for (primary)
ClamAV-clamd
Jan 20 01:54:19 cdc amavis[1588]: Found secondary av scanner ClamAV-clamscan at
/usr/bin/clamscan
Jan 20 01:54:19 cdc amavis[1588]: TROUBLE in pre_loop_hook: db_init: BDB bad db
env. at /var/spool/amavisd/db: Invalid argument, . at (eval 37) line 244.
[root@cdc amavisd]# ls -al /var/spool/amavisd/db/
total 8
drwx------ 2 amavis amavis 4096 Jan 20 01:48 .
drwx------ 5 amavis amavis 4096 Jan 20 01:49 ..
This is a FC4-updated machine.
[root@cdc amavisd]# rpm -V amavisd-new
[root@cdc amavisd]# rpm -q amavisd-new
amavisd-new-2.3.3-4
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
17 years, 10 months
[Bug 79360] Net::Ping succeeds regardless of port assignment
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Net::Ping succeeds regardless of port assignment
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=79360
jvdias(a)redhat.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution| |NOTABUG
CC| |ville.skytta(a)iki.fi
------- Additional Comments From jvdias(a)redhat.com 2006-01-19 18:19 EST -------
I'm not sure this is actually a bug.
As the Net::Ping manual states:
$p->service_check( { 0 | 1 } );
Set whether or not the connect behavior should enforce remote service
availability as well as reachability. Normally, if the remote server
reported ECONNREFUSED, it must have been reachable because of the
status packet that it reported. With this option enabled, the full
three-way tcp handshake must have been established successfully before
it will claim it is reachable.
So adding
$p->service_check(1);
before the
$p->ping($host);
in the example script attachment makes it only succeed if a tcp server
is actually listening to the $port on $host, which I believe was the
intent, and which resolves the problem described in this bug.
Yes, I agree if a port is specified for a TCP ping, a full connect(2) attempt
should be made, but this is not how Net::Ping was designed or documented to
work - a tcp ping only verifies that the host is reachable, unless the
service_check(1) option is specified .
Hence, this bug is being closed as NOTABUG - if you disagree, please re-open it.
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
17 years, 10 months
[Bug 74884] DateManip complains of Malformed UTF-8
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: DateManip complains of Malformed UTF-8
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=74884
jvdias(a)redhat.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |CLOSED
Resolution| |CURRENTRELEASE
Fixed In Version| |perl-5.8.0-90.4
------- Additional Comments From jvdias(a)redhat.com 2006-01-19 17:33 EST -------
This is definitely no longer a bug with all current perl versions in all
Red Hat linux releases, including the perl-5.8.0+ in RHEL-3 .
o perl no longer complains about invalid UTF8 in comments
o The Date::Manip module no longer contains invalid UTF-8
This bug can now be closed.
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
17 years, 10 months