Beiträge von klou

https://github.com/openmediavault/openmediavault/issues/178

Looks like future jobs will not use the ssh-agent and instead pass in the key directly.

Thanks, Volker!

Sizes vary ... the smallest one is 5 gb or so. That's the one I ran manually, via GUI. Data didn't change, so didn't take long.

Do you know if omv_kill_children is supposed to cleanup the agent processes as well?

/etc/cron.d/openmediavault-rsync

34 15 */1 * * root /var/lib/openmediavault/cron.d/rsync-7efcf03a-70d3-4818-b634-084df6e5ec8c >/dev/null 2>&1

/var/lib/openmediavault/cron.d/rsync-7efcf03a-70d3-4818-b634-084df6e5ec8c

#!/bin/sh
# This configuration file is auto-generated.
# WARNING: Do not edit this file, your changes will be lost.
. /usr/share/openmediavault/scripts/helper-functions
cleanup() {
  omv_kill_children $$
  rm -f /var/run/rsync-7efcf03a-70d3-4818-b634-084df6e5ec8c
  exit
}
[ -e /var/run/rsync-7efcf03a-70d3-4818-b634-084df6e5ec8c ] && exit 1
if ! omv_is_mounted "/srv/dev-disk-by-label-shares" ; then
    omv_error "Destination storage device not mounted at </srv/dev-disk-by-label-shares>!"
    exit 1
fi
trap cleanup 0 1 2 5 15
touch /var/run/rsync-7efcf03a-70d3-4818-b634-084df6e5ec8c
omv_log "Please wait, syncing <root@<snip>://home/DCbackups> to </srv/dev-disk-by-label-shares/Configs> ...\n"
eval $(ssh-agent) >/dev/null
ssh-add /etc/ssh/openmediavault-1d5b75eb-7931-4c74-bb59-6663c3537bed >/dev/null
rsync --verbose --log-file="/var/log/rsync.log" --rsh "ssh -p 22" --recursive --times --archive 'root@<snip>://home/DCbackups' '/srv/dev-disk-by-label-shares/Configs' & wait $!
omv_log "\nThe synchronisation has completed successfully."
~

So, I have 6 rsync jobs, and each time one runs, it looks like it generates its own ssh-agent process but never cleans up upon completion.

I just killed all existing ssh-agent processes, and ran a rsync job manually, and there it is. Subsequent runs generated additional processes.

I'm using Arakkis 4.1.11 on two systems -- and configured a few rsync jobs between them (and other machines). Rsync jobs are only configured on one of these, and they all use passwordless SSH with a Public Key Auth, so the Certificate is in the OMV Certificate store.

On the OMV box that has all of these jobs, it appears that ssh-agent gets spawned > 20 times, nightly (at 0:00). So, I've got something like 40+ ssh-agent processes sitting/sleeping on the box, since it was restarted 2 days ago.

Is this standard behavior? Has anybody else seen this?