Re: 2.6.2alpha question.
Benjamin - thanks! Both the autogen fix and your patch are committed in r1623. FWIW, we don't monitor the SF trackers, so if you (or anyone) have other patches to submit, please mention it on the mailing list. "Clean out and hide the SF tracker" is on my TODO list... Dustin -- Storage Software Engineer http://www.zmanda.com
Re: release of amanda-2.6.1
Firstly, I removed the 2 redundant lines in my patch -> compile and
build seems still to be ok.
Then, I changed the distver line to 11.1 -> now the error re-occurs:
"
cont...@fiume:~/done/RPMs/amanda> sudo rpmbuild
-ba /usr/src/packages/SPECS/amanda.spec root's password:
error: parse error in expression
error: /usr/src/packages/SPECS/amanda.spec:363: parseExpressionBoolean
returns -1 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.13551
etc.
regards,
Charles
On Thu, 29 Jan 2009 10:44:15 -0500
"Dustin J. Mitchell" wrote:
> Your diff contained two redundant lines (disttag, which is already set
> on line 111 and dist, which is already set on 109), and set distver to
> 11 instead of 11.1.
>
> On Thu, Jan 29, 2009 at 4:41 AM, Charles Stroom
> wrote:
> > error: /usr/src/packages/SPECS/amanda.spec:363:
> > parseExpressionBoolean
>
> 363 %if %{disttag} == rhel && %{distver} == 3
>
> On this line, it seems that rpm can't handle the "." in distver. Just
> to verify, can you alter your patch to re-add the ".1" in distver and
> verify that the failure recurs? If this is the case, we'll need to
> adjust our numbering scheme (probably adopting the four-digit format
> of suse_version).
>
> Dustin
>
> --
> Storage Software Engineer
> http://www.zmanda.com
Re: 2.6.2alpha question.
On Thu, Jan 29, 2009 at 08:24:34AM -0500, Benjamin Lewis wrote:
>
> I should note that there's also a bug in the autogen script itself:
>
> die() {
> echo x"$...@}" | sed s/^x//
> exit 1
> }
>
> Maybe that works on Linux where /bin/sh and /bin/bash are identical but
> on Solaris you'll need something like
>
> die() {
> echo x"$...@}" | sed 's/^x//'
> exit 1
> }
By way of explanation for those not old enough to have been around
when it was the case (unlike myself), early unix shells recognized
two symbols for piping, the vertical bar (|) and the caret (^).
This "feature" was carried through several unix shells, notably,
the Thompson, Mashey, and Bourne shells. As Solaris' /bin/sh is
the Bourne shell, the caret in the first version needs quoting.
jl
--
Jon H. LaBadie j...@jgcomp.com
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)
Re: Error on backup
No, it's not a system call returning with setting errno to 2. It is tar exiting with an exit status of 2. Check 'man tar' or 'info tar'. Check the DETAIL section of the report, it give the tar error message. Jean-Louis donald.ritc...@comed.com wrote: And error code 2 can be found in either /usr/include/errno.h or /usr/include/sys/errno.h, depending on your particular version of UNIX and how it structures the include files. (On Tru64 UNIX, the code is 'file or directory not found'.) Don Ritchey -Original Message- From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org] On Behalf Of Jean-Louis Martineau Sent: Thursday, January 29, 2009 06:01 To: Prashant Ramhit Cc: amanda-users Subject: Re: Error on backup The DETAIL section of the report list the output of tar, you should see why it failed (exit with code 2). Jean-Louis Prashant Ramhit wrote: Hi All. Does any one knows what this error code means FAILURE AND STRANGE DUMP SUMMARY: backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump (22576) /usr/bin/tar returned 2] backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump to tape failed] And how can I troubleshoot that, Thanks Prashant - ** This e-mail and any of its attachments may contain Commonwealth Edison Company proprietary information, which is privileged, confidential, or subject to copyright belonging to Commonwealth Edison Company or its affiliates. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You. **
Re: release of amanda-2.6.1
Your diff contained two redundant lines (disttag, which is already set
on line 111 and dist, which is already set on 109), and set distver to
11 instead of 11.1.
On Thu, Jan 29, 2009 at 4:41 AM, Charles Stroom
wrote:
> error: /usr/src/packages/SPECS/amanda.spec:363: parseExpressionBoolean
363 %if %{disttag} == rhel && %{distver} == 3
On this line, it seems that rpm can't handle the "." in distver. Just
to verify, can you alter your patch to re-add the ".1" in distver and
verify that the failure recurs? If this is the case, we'll need to
adjust our numbering scheme (probably adopting the four-digit format
of suse_version).
Dustin
--
Storage Software Engineer
http://www.zmanda.com
Re: 2.6.2alpha question.
On Thursday 29 January 2009, Benjamin Lewis wrote:
>Gene Heskett wrote:
>> On Wednesday 28 January 2009, Benjamin Lewis wrote:
>>> I think it would be a good idea to pick some other name to test with
>>> since the .name TLD has come into existence. host.name and a.host.name
>>> both resolve. There's no reason that not.a.host.name couldn't resolve
>>> someday.
>>
>> Now that makes sense. As Jean-Louis would say, patches to configure.in
>> welcome. :-)
>
>I submitted a patch to config/amanda/dumpers.m4 to change
>not.a.host.name to nosuchhost.amanda.org in the configure script. The
>Request ID is 2545424. The patch was developed against the
>amanda-2.6.2alpha-20090128 source code.
>
Thanks Ben. In the case of a user using opendns for his dns servers, it won't
do any good, they are miss-configured. Trouble ticket opened yesterday, but
I've not heard back from them. In the meantime I'm back to using verizons
dns servers with their 95% uptime.
>The patch is completely untested by me because I can't get the autogen
>script to run (probably GLIB related) on my workstation and I don't have
>time to fool with that at the moment.
>
>I should note that there's also a bug in the autogen script itself:
>
>die() {
>echo x"$...@}" | sed s/^x//
>exit 1
>}
>
>Maybe that works on Linux where /bin/sh and /bin/bash are identical but
>on Solaris you'll need something like
>
>die() {
>echo x"$...@}" | sed 's/^x//'
>exit 1
>}
I am not that much of a shell guru, but shouldn't the latter also work with
bash/sh?
>Thanks,
>
>-Ben
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
I judge a religion as being good or bad based on whether its adherents
become better people as a result of practicing it.
- Joe Mullally, computer salesman
Re: 2.6.2alpha question.
Gene Heskett wrote:
> On Wednesday 28 January 2009, Benjamin Lewis wrote:
>> I think it would be a good idea to pick some other name to test with
>> since the .name TLD has come into existence. host.name and a.host.name
>> both resolve. There's no reason that not.a.host.name couldn't resolve
>> someday.
> Now that makes sense. As Jean-Louis would say, patches to configure.in
> welcome. :-)
I submitted a patch to config/amanda/dumpers.m4 to change
not.a.host.name to nosuchhost.amanda.org in the configure script. The
Request ID is 2545424. The patch was developed against the
amanda-2.6.2alpha-20090128 source code.
The patch is completely untested by me because I can't get the autogen
script to run (probably GLIB related) on my workstation and I don't have
time to fool with that at the moment.
I should note that there's also a bug in the autogen script itself:
die() {
echo x"$...@}" | sed s/^x//
exit 1
}
Maybe that works on Linux where /bin/sh and /bin/bash are identical but
on Solaris you'll need something like
die() {
echo x"$...@}" | sed 's/^x//'
exit 1
}
Thanks,
-Ben
--
Benjamin Lewis, CISSP
Security Analyst, Identity and Access Management
IT Networks & Security
Purdue University
smime.p7s
Description: S/MIME Cryptographic Signature
Re: Error on backup
The DETAIL section of the report list the output of tar, you should see why it failed (exit with code 2). Jean-Louis Prashant Ramhit wrote: Hi All. Does any one knows what this error code means FAILURE AND STRANGE DUMP SUMMARY: backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump (22576) /usr/bin/tar returned 2] backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump to tape failed] And how can I troubleshoot that, Thanks Prashant
Re: release of amanda-2.6.1
Paddy, thanks. I tried to create a suse binary 11.1 rpm as I did for 2.6.0p2, but it failed. After an "rpm -i amanda-2.6.1-1.rhel4.src.rpm", I did the rpmbuild: " cont...@fiume:~/done/RPMs/amanda> sudo rpmbuild -ba /usr/src/packages/SPECS/amanda.spec root's password: error: parse error in expression error: /usr/src/packages/SPECS/amanda.spec:363: parseExpressionBoolean returns -1 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.63934 + umask 022 + cd /usr/src/packages/BUILD + cd /usr/src/packages/BUILD + rm -rf amanda-2.6.1 + /usr/bin/gzip -dc /usr/src/packages/SOURCES/amanda-2.6.1.tar.gz + tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd amanda-2.6.1 ++ /usr/bin/id -u + '[' 0 = 0 ']' + /bin/chown -Rhf root . ++ /usr/bin/id -u + '[' 0 = 0 ']' + /bin/chgrp -Rhf root . + /bin/chmod -Rf a+rX,u+w,g-w,o-w . + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.6827 + umask 022 + cd /usr/src/packages/BUILD + /bin/rm -rf /var/tmp/amanda-2.6.1-1.suse11.1-root-buildroot ++ dirname /var/tmp/amanda-2.6.1-1.suse11.1-root-buildroot + /bin/mkdir -p /var/tmp + /bin/mkdir /var/tmp/amanda-2.6.1-1.suse11.1-root-buildroot + cd amanda-2.6.1 + exit 0 Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/amanda-2.6.1-1.suse11.1-root-buildroot Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/amanda-2.6.1-1.suse11.1-root-buildroot Wrote: /usr/src/packages/SRPMS/amanda-2.6.1-1.suse11.1.src.rpm cont...@fiume:~/done/RPMs/amanda> " I could see that the amanda.spec file had the definition for suse 11.1 in it, but not all as was in Ingo's amanda.spec file for 2.6.0p2. So I modified the new amanda.spec file as follows: " fiume:/usr/src/packages/SPECS # rcsdiff -r1.1 -r1.2 amanda.spec === RCS file: RCS/amanda.spec,v retrieving revision 1.1 retrieving revision 1.2 diff -r1.1 -r1.2 129c129,131 < %define distver 11.1 --- > %define dist SuSE > %define disttag suse > %define distver 11 " With this modification, the rpmbuild compiled and came to a normal end, but I am of course not sure this is all to it. Not have I yet installed the 2.6.1 version. Regards, Charles On Wed, 28 Jan 2009 13:52:45 -0800 Paddy Sreenivasan wrote: > Charles, > > We have added source rpm to the downloads page. It says "rhel4" > because this source rpm was built on rhel4 > machine. > > thanks > Paddy > > On Wed, Jan 28, 2009 at 1:06 PM, Charles Stroom > wrote: > > Will a source in RPM "amanda-2.6.1.noarch.src.rpm" become available > > as it was for 2.6.0.p2? > > > > Regards, > > > > Charles > > > > > > > > On Mon, 26 Jan 2009 12:58:01 -0500 > > Jean-Louis Martineau wrote: > > > >> Hello, > >> > >> The Amanda core team is pleased to announce the release of Amanda > >> 2.6.1. Thanks to everyone that tested 2.6.1b1 and 2.6.1b2 and > >> provided feedback. > >> > >> > >> Source tarballs are available from > >> > >> * http://www.amanda.org > > > > > > -- > Amanda http://amanda.zmanda.com > ZRM for MySQL http://www.zmanda.com/backup-mysql.html
Error on backup
Hi All. Does any one knows what this error code means FAILURE AND STRANGE DUMP SUMMARY: backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump (22576) /usr/bin/tar returned 2] backupserver /mnt/fileserver1/bb-share/project/ lev 0 FAILED [dump to tape failed] And how can I troubleshoot that, Thanks Prashant
