A bug in amstatus should not prevent your backup to run correctly.
Changing amdump.1 can't help to start a backup run (amdump).
Your backup should run correctly even if amstatus crash.

Which locale are you using?

Jean-Louis

Dominik Schips wrote:

Hello,

since Saturday (2008-05-31) my ananda backup didn't run.
A closer look when I run the command /usr/sbin/amstatus DailyFull get me
this output:

Day '31' out of range 1..30 at /usr/sbin/amstatus line 1148
using /var/lib/amanda/DailyFull/log/amdump.1 from Sa Mai 21 15:30:08
CEST

I coudn't find any errors or someting else in the logs.

Because I didn't know what went wrong I had to fake (change) the date
in /var/lib/amanda/DailyFull/log/amdump.1 from .... 31.... to ....30...

Know the backup starts and I hope that it finish correct without
problem.

The question is what can cause this error
"Day '31' out of range 1..30 at /usr/sbin/amstatus line 1148"?

I use Amanda 2.4.4p3 from Debian sarge. I know it's old, but there
wasn't time to make a update to Etch. This is on my todo within the nex
4 weeks.

Best regards,

Dominik