Posts by bkeadle

    I'm receiving email alerts showing:

    error: error creating output file /var/log/nginx/openmediavault-webgui_access.log.1.gz: File exists
    error: error creating output file /var/log/nginx/openmediavault-webgui_error.log.1.gz: File exists
    run-parts: /etc/cron.daily/logrotate exited with return code 1

    shouldn't logrotate be able to handle deleting previously rotated logs?

    Figured it out

    I modified /usr/share/openmediavault/mkconf/rsync:

    what is correct? my guess at retrieving the comment value?

    oh! I check the syntax of my script and I had an error. It's doing what I hoped! Thanks for the confirmation!

    Figured it out

    I modified /usr/share/openmediavault/mkconf/rsync:

    I'm doing some custom scripting, to be able to log start and end times of an rsync job. I'm wanting to utilize the Comment field of an rsync job as the value for the log file. How can I retrieve this information? Looking at the rsync mkconf I see this code:

    srcuri=$(omv_config_get "//services/rsync/jobs/job[uuid='${uuid}']/src")
    destsfref=$(omv_config_get "//services/rsync/jobs/job[uuid='${uuid}']/dest")
    desturi=$(omv_get_sharedfolder_path "${destsfref}")
    desturiarg=$(omv_escapeshellarg "${desturi}")
    destmntdir=$(omv_get_sharedfolder_mount_dir "${destsfref}")

    which makes me think there is something similar to retrieve the Comment value. I thought...hoped...this would work:

    logfile=$(omv_config_get "//services/rsync/jobs/job[uuid='${uuid}']/comment")

    Am I close? Any suggestions?

    I did make some progress on this. I added lines 4,5 and 9,10

    Which creates an appended log /var/log/rsync-OMV.log

    What I'd really like to do is to be able to reference the rsync job's destination or comment, so that a job can append to a job-specific log file:

    e.g. /var/log/rsync-Installs.log

    Is there some reference/variable that I can read from the job to get this Destination or Comment value? e.g.:

    o "echo \"\$NOW BEGIN: ${srcuri}\" >> /var/log/rsync-${dst}.log" -n\

    In fact, I would like to know how to retrieve the Comment value for the job, and I would simply make the comment the filename of the log file, e.g.: /var/log/rsync-Installs.log. Reviewing this code:

    destsfref=$(omv_config_get "//services/rsync/jobs/job[uuid='${uuid}']/dest")

    I was wondering if there was a similar command to get the Comment value. I had guessed it to be like:

    logfile=$(omv_config_get "//services/rsync/jobs/job[uuid='${uuid}']/comment")

    but that didn't work.

    Thank you for your reply:

    I have a backup of the orginal(?), but the current sources list was found elsewhere in the forums to get something else working. I tried putting back the original (just a simply file copy is all?), but still got the same results:

    I have two semi-identical OMV installations. The one I can install open-iscsi just fine. The other, I get:

    $ apt-get install open-iscsi
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Package open-iscsi is not available, but is referred to by another package.
    This may mean that the package is missing, has been obsoleted, or
    is only available from another source
    E: Package 'open-iscsi' has no installation candidate

    both have the same /etc/apt/sources.list

    So why does one work but the other doesn't? How do I fix the other?

    I found I can specify a specific binding:

    # listen [::]:80 default_server ipv6only=off;

    I have an OMV machine with 2 NICs. I only want OMV listening to one NIC so that I can have a different web service bound to the second nic (for BackupPC).

    After having added the second NIC, I was suprised to see OMV having bound to the second IP as well. How can I keep OMV "connected" to a single NIC?

    I got that command from as revealed from OMV's cron job.I set up key exchange for root user, and changed the job to login as root and removed the extra options and it works as expected.

    I'm sure now that the problem is with trying to ssh as my remote-backup user...and I'm prompted for a password.

    I even tried this:

    and still getting prompted for remote-backup's password