Re: 3.1.2 : Problems with mails?
Am 16.09.2010 21:43, schrieb Dustin J. Mitchell: On Thu, Sep 16, 2010 at 2:14 PM, Stefan G. Weichinger s...@amanda.org wrote: Tested, works now! Great! Jean-Louis just reviewed the patch, and it's committed in r3411. Can't pull that patch anymore from http://github.com/djmitche/amanda/commit/z11963.patch ? Could you pls provide me that patch, I would like to use it for a (mostly using stable-ebuilds) gentoo-host. Thanks, Stefan
Re: 3.1.2 : Problems with mails?
Am 16.09.2010 23:35, schrieb Dustin J. Mitchell:
On Thu, Sep 16, 2010 at 4:24 PM, Stefan G. Weichinger
s...@amanda.org wrote:
Sure ... what should that ebuild pull in and where from?
It should probably pull from the sourceforge subversion tree:
http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/svn-sources/index.html
Attached my poor draft ... it pulls sources in already but fails with
automake ...
I know too less about that to debug that ... any hint?
Stefan
# Copyright 1999-2010 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/app-backup/amanda/amanda-2.6.1_p2.ebuild,v
1.4 2010/05/08 19:48:53 robbat2 Exp $
EAPI=3
inherit autotools eutils perl-module subversion
MY_P=${P/_}
DESCRIPTION=The Advanced Maryland Automatic Network Disk Archiver
HOMEPAGE=http://www.amanda.org/;
ESVN_REPO_URI=https://amanda.svn.sourceforge.net/svnroot/amanda/amanda/trunk;
#ESVN_PROJECT=amanda/trunk
#ESVN_PROJECT=3.2.0alpha
LICENSE=as-is
SLOT=0
KEYWORDS=~amd64 ~ppc ~ppc64 ~sparc ~x86
RDEPEND=sys-libs/readline
virtual/inetd
sys-apps/gawk
app-arch/tar
=dev-lang/perl-5.6
app-arch/dump
net-misc/openssh
=dev-libs/glib-2.24.0
nls? ( virtual/libintl )
s3? ( =net-misc/curl-7.10.0 )
samba? ( net-fs/samba )
kerberos? ( app-crypt/mit-krb5 )
xfs? ( sys-fs/xfsdump )
!minimal? (
virtual/mailx
app-arch/mt-st
sys-block/mtx
gnuplot? ( sci-visualization/gnuplot )
app-crypt/aespipe
app-crypt/gnupg
)
DEPEND=${RDEPEND}
dev-util/pkgconfig
nls? ( sys-devel/gettext )
IUSE=gnuplot ipv6 kerberos minimal nls s3 samba xfs
S=${WORKDIR}/${MY_P}
MYFILESDIR=${T}/files
ENVDIR=/etc/env.d
ENVDFILE=97amanda
TMPENVFILE=${T}/${ENVDFILE}
# This is a complete list of Amanda settings that the ebuild takes from the
# build environment. This allows users to alter the behavior of the package as
# upstream intended, but keeping with Gentoo style. We store a copy of them in
# /etc/env.d/97amanda during the install, so that they are preserved for future
# installed. This variable name must not start with AMANDA_, as we do not want
# it captured into the env file.
ENV_SETTINGS_AMANDA=
AMANDA_GROUP_GID AMANDA_GROUP_NAME
AMANDA_USER_NAME AMANDA_USER_UID AMANDA_USER_SH AMANDA_USER_HOMEDIR
AMANDA_USER_GROUPS
AMANDA_SERVER AMANDA_SERVER_TAPE AMANDA_SERVER_INDEX
AMANDA_TAR_LISTDIR AMANDA_TAR
AMANDA_PORTS_UDP AMANDA_PORTS_TCP AMANDA_PORTS_BOTH AMANDA_PORTS
AMANDA_CONFIG_NAME AMANDA_TMPDIR
amanda_variable_setup() {
# Setting vars
local currentamanda
# Grab the current settings
currentamanda=$(set | egrep ^AMANDA_ | grep -v
'^AMANDA_ENV_SETTINGS' | xargs)
# First we set the defaults
[ -z ${AMANDA_GROUP_GID} ] AMANDA_GROUP_GID=87
[ -z ${AMANDA_GROUP_NAME} ] AMANDA_GROUP_NAME=amanda
[ -z ${AMANDA_USER_NAME} ] AMANDA_USER_NAME=amanda
[ -z ${AMANDA_USER_UID} ] AMANDA_USER_UID=87
[ -z ${AMANDA_USER_SH} ] AMANDA_USER_SH=/bin/bash
[ -z ${AMANDA_USER_HOMEDIR} ] AMANDA_USER_HOMEDIR=/var/spool/amanda
[ -z ${AMANDA_USER_GROUPS} ]
AMANDA_USER_GROUPS=${AMANDA_GROUP_NAME}
# This installs Amanda, with the server. However, it could be a client,
# just specify an alternate server name in AMANDA_SERVER.
[ -z ${AMANDA_SERVER} ] AMANDA_SERVER=${HOSTNAME}
[ -z ${AMANDA_SERVER_TAPE} ] AMANDA_SERVER_TAPE=${AMANDA_SERVER}
[ -z ${AMANDA_SERVER_INDEX} ]
AMANDA_SERVER_INDEX=${AMANDA_SERVER}
[ -z ${AMANDA_TAR_LISTDIR} ]
AMANDA_TAR_LISTDIR=${AMANDA_USER_HOMEDIR}/tar-lists
[ -z ${AMANDA_CONFIG_NAME} ] AMANDA_CONFIG_NAME=DailySet1
[ -z ${AMANDA_TMPDIR} ] AMANDA_TMPDIR=/var/tmp/amanda
[ -z ${AMANDA_DBGDIR} ] AMANDA_DBGDIR=$AMANDA_TMPDIR
# These are left empty by default
[ -z ${AMANDA_PORTS_UDP} ] AMANDA_PORTS_UDP=
[ -z ${AMANDA_PORTS_TCP} ] AMANDA_PORTS_TCP=
[ -z ${AMANDA_PORTS_BOTH} ] AMANDA_PORTS_BOTH=
[ -z ${AMANDA_PORTS} ] AMANDA_PORTS=
# What tar to use
[ -z ${AMANDA_TAR} ] AMANDA_TAR=/bin/tar
# Now pull in the old stuff
if [ -f ${ROOT}${ENVDIR}/${ENVDFILE} ]; then
# We don't just source it as we don't want everything in there.
eval $(egrep ^AMANDA_ ${ROOT}${ENVDIR}/${ENVDFILE} | grep
-v '^AMANDA_ENV_SETTINGS')
fi
# Re-apply the new settings if any
[ -n ${currentamanda} ] eval `echo ${currentamanda}`
}
pkg_setup() {
amanda_variable_setup
enewgroup ${AMANDA_GROUP_NAME} ${AMANDA_GROUP_GID}
enewuser ${AMANDA_USER_NAME} ${AMANDA_USER_UID} ${AMANDA_USER_SH}
${AMANDA_USER_HOMEDIR} ${AMANDA_USER_GROUPS}
}
src_unpack() {
Re: 3.1.2 : Problems with mails?
On Fri, Sep 17, 2010 at 7:51 AM, Stefan G. Weichinger s...@amanda.org wrote: Attached my poor draft ... it pulls sources in already but fails with automake ... I know too less about that to debug that ... any hint? You should probably base it on the 3.1.2 ebuild - robbat made a number of changes. As for the automake errors - if you look at the autogen script http://github.com/zmanda/amanda/blob/master/autogen You'll see it does a number of things before calling aclocal and the other autotools. You'll need to replicate that in the svn ebuild. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.1.2 : Problems with mails?
Am 17.09.2010 20:49, schrieb Dustin J. Mitchell: You should probably base it on the 3.1.2 ebuild - robbat made a number of changes. It is based on the current amanda-3.1.2-r1.ebuild in portage. As for the automake errors - if you look at the autogen script http://github.com/zmanda/amanda/blob/master/autogen You'll see it does a number of things before calling aclocal and the other autotools. You'll need to replicate that in the svn ebuild. ok, I try ... thanks ...
Re: gentoo-ebuild for beta-release (was: 3.1.2 : Problems with mails?)
Am 17.09.2010 20:49, schrieb Dustin J. Mitchell:
As for the automake errors - if you look at the autogen script
http://github.com/zmanda/amanda/blob/master/autogen
You'll see it does a number of things before calling aclocal and the
other autotools. You'll need to replicate that in the svn ebuild.
I was lazy and simply call autogen from within the ebuild.
A bit ugly but it works ... some redundant steps done, I assume.
But, hey, it's beta-stuff ;-)
Wanna test?
I successfully built it right now on two separate machines.
Stefan
# Copyright 1999-2010 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/app-backup/amanda/amanda-2.6.1_p2.ebuild,v
1.4 2010/05/08 19:48:53 robbat2 Exp $
EAPI=3
inherit autotools eutils perl-module subversion
MY_P=${P/_}
DESCRIPTION=The Advanced Maryland Automatic Network Disk Archiver
HOMEPAGE=http://www.amanda.org/;
ESVN_REPO_URI=https://amanda.svn.sourceforge.net/svnroot/amanda/amanda/trunk;
#ESVN_PROJECT=amanda/trunk
#ESVN_PROJECT=3.2.0alpha
LICENSE=as-is
SLOT=0
KEYWORDS=~amd64 ~ppc ~ppc64 ~sparc ~x86
RDEPEND=sys-libs/readline
virtual/inetd
sys-apps/gawk
app-arch/tar
=dev-lang/perl-5.6
app-arch/dump
net-misc/openssh
=dev-libs/glib-2.24.0
nls? ( virtual/libintl )
s3? ( =net-misc/curl-7.10.0 )
samba? ( net-fs/samba )
kerberos? ( app-crypt/mit-krb5 )
xfs? ( sys-fs/xfsdump )
!minimal? (
virtual/mailx
app-arch/mt-st
sys-block/mtx
gnuplot? ( sci-visualization/gnuplot )
app-crypt/aespipe
app-crypt/gnupg
)
DEPEND=${RDEPEND}
dev-util/pkgconfig
nls? ( sys-devel/gettext )
IUSE=gnuplot ipv6 kerberos minimal nls s3 samba xfs
S=${WORKDIR}/${MY_P}
MYFILESDIR=${T}/files
ENVDIR=/etc/env.d
ENVDFILE=97amanda
TMPENVFILE=${T}/${ENVDFILE}
# This is a complete list of Amanda settings that the ebuild takes from the
# build environment. This allows users to alter the behavior of the package as
# upstream intended, but keeping with Gentoo style. We store a copy of them in
# /etc/env.d/97amanda during the install, so that they are preserved for future
# installed. This variable name must not start with AMANDA_, as we do not want
# it captured into the env file.
ENV_SETTINGS_AMANDA=
AMANDA_GROUP_GID AMANDA_GROUP_NAME
AMANDA_USER_NAME AMANDA_USER_UID AMANDA_USER_SH AMANDA_USER_HOMEDIR
AMANDA_USER_GROUPS
AMANDA_SERVER AMANDA_SERVER_TAPE AMANDA_SERVER_INDEX
AMANDA_TAR_LISTDIR AMANDA_TAR
AMANDA_PORTS_UDP AMANDA_PORTS_TCP AMANDA_PORTS_BOTH AMANDA_PORTS
AMANDA_CONFIG_NAME AMANDA_TMPDIR
amanda_variable_setup() {
# Setting vars
local currentamanda
# Grab the current settings
currentamanda=$(set | egrep ^AMANDA_ | grep -v
'^AMANDA_ENV_SETTINGS' | xargs)
# First we set the defaults
[ -z ${AMANDA_GROUP_GID} ] AMANDA_GROUP_GID=87
[ -z ${AMANDA_GROUP_NAME} ] AMANDA_GROUP_NAME=amanda
[ -z ${AMANDA_USER_NAME} ] AMANDA_USER_NAME=amanda
[ -z ${AMANDA_USER_UID} ] AMANDA_USER_UID=87
[ -z ${AMANDA_USER_SH} ] AMANDA_USER_SH=/bin/bash
[ -z ${AMANDA_USER_HOMEDIR} ] AMANDA_USER_HOMEDIR=/var/spool/amanda
[ -z ${AMANDA_USER_GROUPS} ]
AMANDA_USER_GROUPS=${AMANDA_GROUP_NAME}
# This installs Amanda, with the server. However, it could be a client,
# just specify an alternate server name in AMANDA_SERVER.
[ -z ${AMANDA_SERVER} ] AMANDA_SERVER=${HOSTNAME}
[ -z ${AMANDA_SERVER_TAPE} ] AMANDA_SERVER_TAPE=${AMANDA_SERVER}
[ -z ${AMANDA_SERVER_INDEX} ]
AMANDA_SERVER_INDEX=${AMANDA_SERVER}
[ -z ${AMANDA_TAR_LISTDIR} ]
AMANDA_TAR_LISTDIR=${AMANDA_USER_HOMEDIR}/tar-lists
[ -z ${AMANDA_CONFIG_NAME} ] AMANDA_CONFIG_NAME=DailySet1
[ -z ${AMANDA_TMPDIR} ] AMANDA_TMPDIR=/var/tmp/amanda
[ -z ${AMANDA_DBGDIR} ] AMANDA_DBGDIR=$AMANDA_TMPDIR
# These are left empty by default
[ -z ${AMANDA_PORTS_UDP} ] AMANDA_PORTS_UDP=
[ -z ${AMANDA_PORTS_TCP} ] AMANDA_PORTS_TCP=
[ -z ${AMANDA_PORTS_BOTH} ] AMANDA_PORTS_BOTH=
[ -z ${AMANDA_PORTS} ] AMANDA_PORTS=
# What tar to use
[ -z ${AMANDA_TAR} ] AMANDA_TAR=/bin/tar
# Now pull in the old stuff
if [ -f ${ROOT}${ENVDIR}/${ENVDFILE} ]; then
# We don't just source it as we don't want everything in there.
eval $(egrep ^AMANDA_ ${ROOT}${ENVDIR}/${ENVDFILE} | grep
-v '^AMANDA_ENV_SETTINGS')
fi
# Re-apply the new settings if any
[ -n ${currentamanda} ] eval `echo ${currentamanda}`
}
pkg_setup() {
amanda_variable_setup
enewgroup ${AMANDA_GROUP_NAME} ${AMANDA_GROUP_GID}
enewuser ${AMANDA_USER_NAME} ${AMANDA_USER_UID} ${AMANDA_USER_SH}
${AMANDA_USER_HOMEDIR}
Re: gentoo-ebuild for beta-release (was: 3.1.2 : Problems with mails?)
On Fri, Sep 17, 2010 at 2:48 PM, Stefan G. Weichinger s...@amanda.org wrote: I was lazy and simply call autogen from within the ebuild. A bit ugly but it works ... some redundant steps done, I assume. But, hey, it's beta-stuff ;-) Sounds good to me.. Wanna test? I'm no gentoo dev, but it builds and installs and passes amcheck for me. Now, if it can get put in an overlay, even cooler! Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.1.2 : Problems with mails?
quote who=Dustin J. Mitchell dunno about getting it hosted at overlay-servers, I have to research that ... Lisa, do you have any pointers on that front? Hi Dustin, Unfortunately it's been some time sine I was a Gentoo dev and when I was active overlays were only just coming about. I'm sorry that I'm not able to give any pointers here beyond what might be on gentoo.org. -- Regards, -Lisa http://www.crudvision.com
Re: 3.1.2 : Problems with mails?
Am 18.09.2010 00:34, schrieb Lisa Seelye: quote who=Dustin J. Mitchell Lisa, do you have any pointers on that front? Hi Dustin, Unfortunately it's been some time sine I was a Gentoo dev and when I was active overlays were only just coming about. I'm sorry that I'm not able to give any pointers here beyond what might be on gentoo.org. Thanks, Lisa, we will work that out with the current devs ... Stefan ps: hey, just found your blog and stuff about climbing! I do that as well ... ;-)
Re: 3.1.2 : Problems with mails?
On Fri, Sep 17, 2010 at 5:34 PM, Lisa Seelye l...@thedoh.com wrote: Unfortunately it's been some time sine I was a Gentoo dev and when I was active overlays were only just coming about. I'm sorry that I'm not able to give any pointers here beyond what might be on gentoo.org. OK, thanks! Hopefully you can still help us out with testing the new features in Amanda.. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.1.2 : Problems with mails?
Am 15.09.2010 23:26, schrieb Dustin J. Mitchell: On Wed, Sep 15, 2010 at 2:09 PM, Stefan G. Weichinger s...@amanda.org wrote: Could this also be related to environment variables as in the other case I mentioned here some weeks ago, also with 3.1.2 ... ? That's certainly possible - it sounds like it's outside of Amanda's purview, in any case. I'm not at all familiar with msmtp.. It works with only one recipient in amanda.conf, but not with multiple recps. And I use it/msmtp because I don't want to compile and run postfix on each amanda server, just for getting reportmails sent. I could work around it by setting an alias elsewhere. But it was really just after 3.1.2 that things broke ... maybe 3.1.2 doesn't quote the recps anymore? Stefan
Re: 3.1.2 : Problems with mails?
Am 15.09.2010 23:26, schrieb Dustin J. Mitchell: On Wed, Sep 15, 2010 at 2:09 PM, Stefan G. Weichinger s...@amanda.org wrote: Could this also be related to environment variables as in the other case I mentioned here some weeks ago, also with 3.1.2 ... ? That's certainly possible - it sounds like it's outside of Amanda's purview, in any case. I'm not at all familiar with msmtp.. Additional thought: gentoo-context: amanda-3.1.2 pulls in =dev-libs/glib-2.24.0 ... could that have some changed things?
Re: 3.1.2 : Problems with mails?
On Thu, Sep 16, 2010 at 3:14 AM, Stefan G. Weichinger s...@amanda.org wrote: gentoo-context: amanda-3.1.2 pulls in =dev-libs/glib-2.24.0 ... could that have some changed things? Ah, you're right - Amanda-3.1.2 passes all of the addresses as one space-separated string, while Amanda-2.6.1 lumped the whole command into a single string and thus let the shell break them at space boundaries. I'll have a patch for your experimentation in a little bit. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.1.2 : Problems with mails?
Am 16.09.2010 19:25, schrieb Dustin J. Mitchell: On Thu, Sep 16, 2010 at 3:14 AM, Stefan G. Weichinger s...@amanda.org wrote: gentoo-context: amanda-3.1.2 pulls in =dev-libs/glib-2.24.0 ... could that have some changed things? Ah, you're right - Amanda-3.1.2 passes all of the addresses as one space-separated string, while Amanda-2.6.1 lumped the whole command into a single string and thus let the shell break them at space boundaries. I'll have a patch for your experimentation in a little bit. nice to hear that! ;-) thanks S
Re: 3.1.2 : Problems with mails?
On Thu, Sep 16, 2010 at 12:40 PM, Stefan G. Weichinger s...@amanda.org wrote: nice to hear that! Give this a try: http://github.com/djmitche/amanda/commit/z11963.patch Don't worry about the installcheck hunk. You should be able to apply the amreport hunk in place in /usr/sbin if that's easiest. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.1.2 : Problems with mails?
Am 16.09.2010 19:54, schrieb Dustin J. Mitchell: On Thu, Sep 16, 2010 at 12:40 PM, Stefan G. Weichinger s...@amanda.org wrote: nice to hear that! Give this a try: http://github.com/djmitche/amanda/commit/z11963.patch Don't worry about the installcheck hunk. You should be able to apply the amreport hunk in place in /usr/sbin if that's easiest. amcheck -m mailed ok so far ... the real test will be the amreport after the amdump tonight. amreport daily shows the last report, but I get: $ amreport daily --from-amdump nothing to report on! if I want to force a mail sent ... Thanks for the patch, Stefan
Re: 3.1.2 : Problems with mails?
On Thu, Sep 16, 2010 at 1:06 PM, Stefan G. Weichinger s...@amanda.org wrote: amcheck -m mailed ok so far ... the real test will be the amreport after the amdump tonight. amreport daily shows the last report, but I get: $ amreport daily --from-amdump nothing to report on! if I want to force a mail sent ... --from-amdump is really only meant to be used, well, from amdump :) If you just run 'amreport daily' it will send a report to stdout If you want to mail the report, use amreport daily --mail-text=f...@bar b...@baz Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.1.2 : Problems with mails?
Am 2010-09-16 20:50, schrieb Dustin J. Mitchell: On Thu, Sep 16, 2010 at 1:06 PM, Stefan G. Weichinger s...@amanda.org wrote: amcheck -m mailed ok so far ... forget that one, completely unrelated *sigh* --from-amdump is really only meant to be used, well, from amdump :) Really?? ;-) If you just run 'amreport daily' it will send a report to stdout If you want to mail the report, use amreport daily --mail-text=f...@bar b...@baz Tested, works now! S
Re: 3.1.2 : Problems with mails?
On Thu, Sep 16, 2010 at 2:14 PM, Stefan G. Weichinger s...@amanda.org wrote: Tested, works now! Great! Jean-Louis just reviewed the patch, and it's committed in r3411. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.1.2 : Problems with mails?
Am 2010-09-16 21:43, schrieb Dustin J. Mitchell: On Thu, Sep 16, 2010 at 2:14 PM, Stefan G. Weichinger s...@amanda.org wrote: Tested, works now! Great! Jean-Louis just reviewed the patch, and it's committed in r3411. fine ... considering my own private ebuild here (in an overlay) to pull current development-stuff ... Stefan
Re: 3.1.2 : Problems with mails?
On Thu, Sep 16, 2010 at 4:11 PM, Stefan G. Weichinger s...@amanda.org wrote: considering my own private ebuild here (in an overlay) to pull current development-stuff ... That would be great. We're rapidly heading toward a 3.2.0b1, and the more testing can happen with that, the better the 3.2.0 release will be. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.1.2 : Problems with mails?
On Thu, Sep 16, 2010 at 4:14 PM, Dustin J. Mitchell dus...@zmanda.com wrote: That would be great. We're rapidly heading toward a 3.2.0b1, and the more testing can happen with that, the better the 3.2.0 release will be. In fact (and sorry for the double-post .. I've probably had too much coffee), if you can share that overlay on one of the Gentoo overlay servers, or even on Github, I suspect that at least Lisa, and likely several others, would find it very useful. Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.1.2 : Problems with mails?
Am 2010-09-16 23:15, schrieb Dustin J. Mitchell: On Thu, Sep 16, 2010 at 4:14 PM, Dustin J. Mitchell dus...@zmanda.com wrote: That would be great. We're rapidly heading toward a 3.2.0b1, and the more testing can happen with that, the better the 3.2.0 release will be. In fact (and sorry for the double-post .. I've probably had too much coffee), if you can share that overlay on one of the Gentoo overlay servers, or even on Github, I suspect that at least Lisa, and likely several others, would find it very useful. Sure ... what should that ebuild pull in and where from? Does it take longer to point at than to set it up? ;-) dunno about getting it hosted at overlay-servers, I have to research that ... Stefan
Re: 3.1.2 : Problems with mails?
On Thu, Sep 16, 2010 at 4:24 PM, Stefan G. Weichinger s...@amanda.org wrote: Sure ... what should that ebuild pull in and where from? It should probably pull from the sourceforge subversion tree: http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/svn-sources/index.html Does it take longer to point at than to set it up? ;-) Perhaps, but it seems to be the New Way Things Are Done in Gentoo, and certainly robbat would have an easier time putting a new version into testing in the main tree if he had an existing ebuild in use by a number of testers. dunno about getting it hosted at overlay-servers, I have to research that ... Lisa, do you have any pointers on that front? Dustin -- Open Source Storage Engineer http://www.zmanda.com
Re: 3.1.2 : Problems with mails?
Am 14.09.2010 22:51, schrieb Stefan G. Weichinger: Am 14.09.2010 22:25, schrieb Stefan G. Weichinger: Seems to be related to the mailwrapper in gentoo ... gotta dig further. The working one has postfix installed, the non-working only msmtp ... but I don't get why it worked with 2.6.1p2 ... Could this also be related to environment variables as in the other case I mentioned here some weeks ago, also with 3.1.2 ... ? Stefan
Re: 3.1.2 : Problems with mails?
On Wed, Sep 15, 2010 at 2:09 PM, Stefan G. Weichinger s...@amanda.org wrote: Could this also be related to environment variables as in the other case I mentioned here some weeks ago, also with 3.1.2 ... ? That's certainly possible - it sounds like it's outside of Amanda's purview, in any case. I'm not at all familiar with msmtp.. Dustin -- Open Source Storage Engineer http://www.zmanda.com
3.1.2 : Problems with mails?
For a while I have problems with missing mails from amanda and I can't quite spot it ... Right now I had to stop an amdump due to config-changes and it told me: $ amcleanup -k daily amcleanup: 19 Amanda processes were found running. amcleanup: 1 processes failed to terminate. send-mail: recipient address off...@123.at l...@345.at w@678.at not accepted by the server send-mail: server message: 501 5.1.3 Bad recipient address syntax send-mail: could not send mail (account default from /var/spool/amanda/.msmtprc) Can't send mail: sendmail process failed with error code 65 amcleanup: /var/log/amanda/daily/amdump exists, renaming it. This is a server I right now upgraded to 3.1.2 (2.6.1p2 before). I checked my inbox and the server had correctly sent report-mails in the last weeks. I haven't changed a thing in amanda.conf ... man amanda.conf still says space separated list of operators at your site ... Could someone check/confirm this behavior with multiple recipients? - At another site I don't get report-mails from amdump, but I get the mails from the amcheck in crontab ... and mails from the shell go through fine ... hmmm ... Stefan
Re: 3.1.2 : Problems with mails?
Try to do the same command as amanda do: MAILER=`amgetconf daily mailer` $MAILER -s subject off...@123.at l...@345.at w@678.at Type a small message and end it with ctrl-D Do the email are sent? Jean-Louis Stefan G. Weichinger wrote: For a while I have problems with missing mails from amanda and I can't quite spot it ... Right now I had to stop an amdump due to config-changes and it told me: $ amcleanup -k daily amcleanup: 19 Amanda processes were found running. amcleanup: 1 processes failed to terminate. send-mail: recipient address off...@123.at l...@345.at w@678.at not accepted by the server send-mail: server message: 501 5.1.3 Bad recipient address syntax send-mail: could not send mail (account default from /var/spool/amanda/.msmtprc) Can't send mail: sendmail process failed with error code 65 amcleanup: /var/log/amanda/daily/amdump exists, renaming it. This is a server I right now upgraded to 3.1.2 (2.6.1p2 before). I checked my inbox and the server had correctly sent report-mails in the last weeks. I haven't changed a thing in amanda.conf ... man amanda.conf still says space separated list of operators at your site ... Could someone check/confirm this behavior with multiple recipients? - At another site I don't get report-mails from amdump, but I get the mails from the amcheck in crontab ... and mails from the shell go through fine ... hmmm ... Stefan
Re: 3.1.2 : Problems with mails?
Am 14.09.2010 21:21, schrieb Jean-Louis Martineau: Try to do the same command as amanda do: MAILER=`amgetconf daily mailer` $MAILER -s subject off...@123.at l...@345.at w@678.at Type a small message and end it with ctrl-D Do the email are sent? Email gets sent on my server where /bin/mail belongs to mailx. Email does not get sent on the other server where /bin/mail belongs to ... mailx hmm. But the other server has msmtp installed ... mine not. Seems to be related to the mailwrapper in gentoo ... gotta dig further. Thanks, jlm ...
Re: 3.1.2 : Problems with mails?
Am 14.09.2010 22:25, schrieb Stefan G. Weichinger: Seems to be related to the mailwrapper in gentoo ... gotta dig further. The working one has postfix installed, the non-working only msmtp ... but I don't get why it worked with 2.6.1p2 ... S
