[bug-notifications] [amanda 0004254]: svc:/network/amanda/udp:default always enters maintenance state when amcheck or amservice is run

Mantis Bug Tracker noreply at opencsw.org
Tue May 11 16:41:50 CEST 2010


A NOTE has been added to this issue. 
====================================================================== 
http://www.opencsw.org/mantis/view.php?id=4254 
====================================================================== 
Reported By:                amyrrich
Assigned To:                darin
====================================================================== 
Project:                    amanda
Issue ID:                   4254
Category:                   regular use
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2010-02-03 15:00 CET
Last Modified:              2010-05-11 16:41 CEST
====================================================================== 
Summary:                    svc:/network/amanda/udp:default always enters
maintenance state when amcheck or amservice is run
Description: 
Upgraded from amanda-2.4.4p4,REV=2005.08.05-SunOS5.8-sparc-CSW.pkg to 
manda-2.6.1,REV=2009.05.28_rev=p1-SunOS5.8-sparc-CSW.pkg on the amanda
server, and amcheck to the local host stopped functioning.  Whenever
amcheck or amservice is run, it always transitions the amanda/udp service
into a maintenance state.  amcheck and amservice continue to function fine
with clients that have not been upgraded.  Downgrading back to
amanda-2.4.4p4,REV=2005.08.05-SunOS5.8-sparc-CSW.pkg fixed the issue.

====================================================================== 

---------------------------------------------------------------------- 
 (0007920) darin (manager) - 2010-05-11 16:41
 http://www.opencsw.org/mantis/view.php?id=4254#c7920 
---------------------------------------------------------------------- 
I have never run across this issue but I'll take a look at it and try to
recreate the issue.

What is the amservice command you are running?
What is the amcheck command you are running?



More information about the bug-notifications mailing list