Bug 1074216 - amstatus perl script is broken due to misconfiguration of $PS=""
Summary: amstatus perl script is broken due to misconfiguration of $PS=""
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: amanda
Version: 20
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Petr Hracek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1121359 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-08 23:41 UTC by gcarter
Modified: 2014-08-07 15:30 UTC (History)
4 users (show)

Fixed In Version: amanda-3.3.3-10.fc20
Clone Of:
Environment:
Last Closed: 2014-08-07 15:30:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description gcarter 2014-03-08 23:41:28 UTC
Description of problem:

amstatus is broken because of an incorrect configuration.

Version-Release number of selected component (if applicable):

Amanda 3.3.3

How reproducible:

Type amstatus and you get:

$amandabackup: amstatus
** (process:1062): WARNING **: Can't exec "-eo": No such file or directory at /usr/lib64/perl5/vendor_perl/Amanda/Process.pm line 176.

Steps to Reproduce:
1. amstatus
2.
3.

Actual results:

amstatus should produce an output of the current backup job status.

Expected results:

-bash-4.2$ amstatus DailyAESGI
Using /etc/amanda/DailyAESGI/logs/amdump
From Sat Mar  8 16:07:00 CST 2014

maat.aesgi.com:/home/gcarter 0  38180380k dumping to tape (20486944k done (53.66%)) (16:07:02)

SUMMARY          part      real  estimated
                           size       size
partition       :   1
estimated       :   1             38180380k
flush           :   0         0k
failed          :   0                    0k           (  0.00%)
wait for dumping:   0                    0k           (  0.00%)
dumping to tape :   1  20486944k  38180380k ( 53.66%) (100.00%)
dumping         :   0         0k         0k (  0.00%) (  0.00%)
dumped          :   0         0k         0k (  0.00%) (  0.00%)
wait for writing:   0         0k         0k (  0.00%) (  0.00%)
wait to flush   :   0         0k         0k (100.00%) (  0.00%)
writing to tape :   0         0k         0k (  0.00%) (  0.00%)
failed to tape  :   0         0k         0k (  0.00%) (  0.00%)
taped           :   0         0k         0k (  0.00%) (  0.00%)
  tape 1        :   0         0k         0k (  0.00%) DailyAESGI-5
9 dumpers idle  : no-dumpers
taper status: Writing maat.aesgi.com:/home/gcarter
taper qlen: 0
network free kps:     78976
holding space   :         0k (  0.00%)
 dumper1 busy   :  0:00:00  (  0.00%)
 0 dumpers busy :  0:00:02  ( 99.78%)            not-idle:  0:00:02  ( 93.59%)
 1 dumper busy  :  0:00:00  (  0.22%)


Additional info:

This problem can be corrected by editing:

/usr/lib64/perl5/vendor_perl/Amanda/Constants.pm, line 86

$PS = "";

should be

$PS="/usr/bin/ps";

Please issue a correction to the package maintainer and have this correction applied to Fedora 20 asap.

Amanda is a critical piece of system software.

Comment 1 Bjoern Rasmussen 2014-07-24 18:50:49 UTC
Same problem here. Thanks for the workaround!

Comment 3 Fedora Update System 2014-07-28 13:18:23 UTC
amanda-3.3.3-10.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/amanda-3.3.3-10.fc20

Comment 4 Petr Hracek 2014-07-28 13:20:17 UTC
*** Bug 1121359 has been marked as a duplicate of this bug. ***

Comment 5 Fedora Update System 2014-07-29 02:08:29 UTC
Package amanda-3.3.3-10.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing amanda-3.3.3-10.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-8941/amanda-3.3.3-10.fc20
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2014-08-07 15:30:30 UTC
amanda-3.3.3-10.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.