Re: Backup issues with OpenBSD 4.5 machines

2009-08-24 Thread stan
On Fri, Aug 21, 2009 at 03:53:13PM -0600, Michael Burk wrote: Stan's not alone on this one. I have two OpenBSD 4.5 machines also on Sun SPARC hardware. I had this same trouble a couple months ago with 2.6.1, but didn't have time to look deeper. After seeing this discussion, I built

Error redirecting stderr to fd 52

2009-08-24 Thread John Hein
On a 2.6.1b1 client ... 1251090802.506210: sendbackup: pid 61161 ruid 5001 euid 5001 version 2.6.1b1: start at Sun Aug 23 23:13:22 2009 1251090802.506278: sendbackup: Version 2.6.1b1 1251090802.511032: sendbackup: pid 61161 ruid 5001 euid 5001 version 2.6.1b1: rename at Sun Aug 23 23:13:22 2009

Re: Error redirecting stderr to fd 52

2009-08-24 Thread Jean-Louis Martineau
John Hein wrote: On a 2.6.1b1 client ... Hmm, beta software ... It's not fixed in 2.6.1 neither in 2.6.1p1. You must use the latest 2.6.1p1 snapshot from http://www.zmanda.com/community-builds.php Jean-Louis

Re: Backup issues with OpenBSD 4.5 machines

2009-08-24 Thread Michael Burk
I'm using bsdtcp auth. I'll try 2.5.1 today or tomorrow, to see if I can narrow down the range of releases in which OpenBSD support broke. -- Michael On Mon, Aug 24, 2009 at 5:17 AM, stan st...@panix.com wrote: On Fri, Aug 21, 2009 at 03:53:13PM -0600, Michael Burk wrote: Stan's not alone on

Re: Error redirecting stderr to fd 52

2009-08-24 Thread John Hein
Jean-Louis Martineau wrote at 11:48 -0400 on Aug 24, 2009: John Hein wrote: On a 2.6.1b1 client ... Hmm, beta software ... It's not fixed in 2.6.1 neither in 2.6.1p1. You must use the latest 2.6.1p1 snapshot from http://www.zmanda.com/community-builds.php Building a new

Re: Backup issues with OpenBSD 4.5 machines

2009-08-24 Thread Jean-Louis Martineau
This bug can't be fixed until we understand it. Ask on a OpenBSD list how a write to a blocking pipe can return EAGAIN. Or the pipe semantics changed and they don't default to blocking. You can also try the attached, it check the pipe are opened in blocking mode. Jean-Louis stan wrote: On

failure of backups after reboot

2009-08-24 Thread Chris Hoogendyk
This is a recently configured Amanda 2.5.1p3 setup on a group of E250's running Solaris 9. It has been running smoothly for a few weeks now. Just before building Amanda, I had done a reconfigure reboot to get drivers running for a new tape library. This weekend, after the weekend backups had

Re: Backup issues with OpenBSD 4.5 machines

2009-08-24 Thread stan
On Mon, Aug 24, 2009 at 02:01:09PM -0400, Jean-Louis Martineau wrote: This bug can't be fixed until we understand it. Agreed. Ask on a OpenBSD list how a write to a blocking pipe can return EAGAIN. Or the pipe semantics changed and they don't default to blocking. I already posted the code

Re: failure of backups after reboot

2009-08-24 Thread Jean-Louis Martineau
Chris Hoogendyk wrote: driver: FATAL Did not get DATE line from planner The planner crashed, what's in the amdump.1 log file?

Re: Backup issues with OpenBSD 4.5 machines

2009-08-24 Thread stan
On Mon, Aug 24, 2009 at 02:01:09PM -0400, Jean-Louis Martineau wrote: You can also try the attached, it check the pipe are opened in blocking mode. I will try to test that today. Thanks. -- One of the main causes of the fall of the roman empire was that, lacking zero, they had no way to

Re: failure of backups after reboot

2009-08-24 Thread Chris Hoogendyk
Jean-Louis Martineau wrote: Chris Hoogendyk wrote: driver: FATAL Did not get DATE line from planner The planner crashed, what's in the amdump.1 log file? eclogite:/usr/local/etc/amanda/daily/logs:root# more amdump.1 amdump: start at Mon Aug 24 00:45:00 EDT 2009 amdump: datestamp 20090824

Re: failure of backups after reboot

2009-08-24 Thread Jean-Louis Martineau
Chris Hoogendyk wrote: planner: create debug directory /tmp/amanda: File exists It's a race, both planner and driver tried to create the directory at the same time. Next run should be fine. Jean-Louis

Re: Backup issues with OpenBSD 4.5 machines

2009-08-24 Thread stan
On Mon, Aug 24, 2009 at 02:01:09PM -0400, Jean-Louis Martineau wrote: You can also try the attached, it check the pipe are opened in blocking mode. OK, I applied that to 2.61 (after figuriing out it would not apply to 2.5.2 :-)). Of 4 DLE's on the test OpenBSD machine 3failed with PARTIAL,

[no subject]

2009-08-24 Thread Robert Reilly
Hello List I am using amvault to copy from disk to tape it works great The one problem I see it does not record the label and barcode like it does if it was a backup. I am using the chg-zd-mtx script Any thoughts ? image001.jpgBEGIN:VCARD VERSION:2.1 X-MS-SIGNATURE:YES

Re: Backup issues with OpenBSD 4.5 machines

2009-08-24 Thread stan
On Fri, Aug 21, 2009 at 09:57:36AM -0600, John Hein wrote: stan wrote at 10:56 -0400 on Aug 21, 2009: OK here is the latest on this saga :-) On one of the OpenBSD 4.5 machines I have built 2.5.0p1, and was able to back this machine up successfully (using classic UDP based

Re: How can a write to a blocking pipe return EAGAIN?

2009-08-24 Thread stan
On Mon, Aug 24, 2009 at 10:39:21PM +0200, Bret S. Lambert wrote: On Mon, Aug 24, 2009 at 04:25:39PM -0400, stan wrote: I am trying to get Amanda of a recent vintage working on 4.5. The developrs don't understand how writing to a blocking pipe can return EAGAIN. Should the write just

Re: How can a write to a blocking pipe return EAGAIN?

2009-08-24 Thread stan
On Mon, Aug 24, 2009 at 09:34:50PM +0100, Owain Ainsworth wrote: On Mon, Aug 24, 2009 at 04:25:39PM -0400, stan wrote: I am trying to get Amanda of a recent vintage working on 4.5. The developrs don't understand how writing to a blocking pipe can return EAGAIN. Should the write just

Re: Backup issues with OpenBSD 4.5 machines

2009-08-24 Thread John Hein
stan wrote at 16:59 -0400 on Aug 24, 2009: The firts thing I notice when comparing this function in 2.5.0 vs 2.5.2 is that 2.5.0 does: tv.tv_usec = 0; and 2.5.2 does not. Could thim make a difference? Both do tv.tv_sec = timeout; In 2.5.2, the memset sets the entire struct to

New verbosity in the log when running amcheck after 2.6.2alpha20090824

2009-08-24 Thread Gene Heskett
Greetings; This doesn't look terribly comforting, and occurred apparently at the amcheck phase of a script I wrote to install new amanda snapshots: Aug 24 10:35:34 coyote xinetd[2394]: Starting reconfiguration Aug 24

Re: New verbosity in the log when running amcheck after 2.6.2alpha20090824

2009-08-24 Thread Gene Heskett
...@coyote amanda-2.6.2alpha-20090824]# ls -l /etc/xinetd.d total 92 -rw-r--r-- 1 amanda disk 938 2009-05-09 19:12 amanda -rw-r--r-- 1 root root 938 2009-08-24 10:35 amanda.7g1R7x -rw-r--r-- 1 root root 938 2009-08-24 10:35 amanda.cZ5StE -rw-r--r-- 1 root root 938 2009-08-24 10:35 amanda.dka3RX