Henrik,
amanda 3.4 create shared memory and semaphore and require RW on /dev/shm.
You should report it to fedora since they amanda policy.
Jean-Louis
On 18/02/17 02:19 PM, Henrik Johansson wrote:
Hi,
Sending the amandad.*.debug files from server and client, and an
extract from the clients journalctl.
The extract from journalctl suggests report a bug and add a local policy:
***** Plugin catchall (100.
confidence) suggests **************************
If you believe that amandad
should be allowed write access on the shm directory by default.
Then you should report this as
a bug.
You can generate a local
policy module to allow this access.
Do
allow this access for now by
executing:
# ausearch -c 'amandad' --raw
| audit2allow -M my-amandad
# semodule -X 300 -i
my-amandad.pp
Are there new functions in amanda-3.4, that requires extended
permissions?
Where should I report a bug, amanda or Fedora?
There are an installed amanda-policy:
[root@uw000140 ~]# semodule -v -l | egrep amanda
amanda
Must I add the my-amandad policy after every reboot or when should I
remove it?
BR,
Henrik
On 2017-02-18 14:09, Jean-Louis Martineau wrote:
Henrik,
It looks like the estimate worked, but there is no sendbackup debug
files.
Can you post the amandad.*.debug files, they are in
/var/log/amanda/amandad
Did you checked the system log for error?
Jean-Louis
On 18/02/17 03:07 AM, Henrik Johansson wrote:
> Hi,
>
> Yesterday I upgraded to amanda-version 3.4.2, on my Fedora-24 client.
> It has it has the same error as version 3.4.1, downgraded to 3.3.8
> once again.
>
> BR,
> Henrik
>
> On 2017-02-01 19:32, Henrik Johansson wrote:
>> Hi,
>>
>> I've stored the log- and debug-files in tree tar-files for each day.
>> 2017-01-29 the client had amanda-version 3.4.1:
>> From client /tmp/var_log_amanda_client_DailySet1_20170129.tgz
>> From server /tmp/var_log_amanda_server_DailySet1_20170129.tgz
>> From server /tmp/var_lib_amanda_DailySet1_20170129.tgz
>>
>> 2017-01-30, the client has amanda-version 3.3.8:
>> From client /tmp/var_log_amanda_client_DailySet1_20170130.tgz
>> From server /tmp/var_log_amanda_server_DailySet1_20170130.tgz
>> From server /tmp/var_lib_amanda_DailySet1_20170130.tgz
>>
>> BR;
>> Henrik
>>
>> On 2017-02-01 17:02, Jean-Louis Martineau wrote:
>>> Post more information.
>>>
>>> The amdump.<timestamp>, log.<timestamp>.0 and all debug files.
>>>
>>> Jean-Louis
>>>
>>> On 01/02/17 03:11 AM, Henrik Johansson wrote:
>>> > Hi,
>>> >
>>> > I have a server with CentOS-7 and one client with Fedora-24.
>>> > The server runs amanda 3.3.8, the backups of the client stopped
>>> > working, when the client was upgraded to 3.4.1.
>>> > amcheck says that all is OK
>>> >
>>> > Extract from the backup report:
>>> > DUMP SUMMARY:
>>> > DUMPER
>>> > STATS TAPER STATS
>>> > HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s
>>> > MMM:SS KB/s
>>> > ---------------------------------
>>> > -------------------------------------- --------------
>>> > ...
>>> > <client> /boot 0 -- FLUSH
>>> > <client> /home 0 -- FLUSH
>>> >
>>> > I found a temporary solution and downgraded amanda on the
client to
>>> > previous version 3.3.8.
>>> >
>>> > Are there any permanent solution?
>>> >
>>> > BR,
>>> > Henrik
>>> >
>>
>
