In the following log match, there doesn't seem to be a single timestamp:
/usr/local/cpanel/logs/cpbackup/*.log
This makes it nearly impossible, especially while a backup is already running, to see that is happening, without the aid of utilities such as strace.
It would be very nice to be able to see why a user receives an email like so:
Subject : Backup not completed on srv1.domain.tldcPanel on srv1.domain.tld <cpanel@srv1.domain.tld>Sent : Mon 1/1/0001 12:00 AMTo: user@domain.tld
In this email, the following is sent:
The backup was not able to be completed because timed out waiting for /bin/backup to finish
I like this idea 
In cPanel & WHM version 11.46.1 and newer logs created by the new backup system are more verbose, and have time stamps in the form of YYYY-MM-DD HH:MM:SS
In cPanel & WHM version 11.46.1 and newer logs created by the new backup system are more verbose, and have time stamps in the form of YYYY-MM-DD HH:MM:SS
Backlog logs in cPanel & WHM version 11.46.1 and newer will contain time stamps in the YYYY-MM-DD HH:MM:SS format.
Backlog logs in cPanel & WHM version 11.46.1 and newer will contain time stamps in the YYYY-MM-DD HH:MM:SS format.
Yes, those timestamps would be great. :)
Yes, those timestamps would be great. :)
We shopped around the timestamp format, and this was unanimously preferred:
"""
[2014-07-29 10:41:03 -0500] pkgacct started.
[2014-07-29 10:41:03 -0500] pkgacct version 10 - user : functest01 - tarball: 1 - target mysql : default - split: 0 - incremental: 0 - homedir: 1 - archive version: 3 - running with uid 0
[2014-07-29 10:41:03 -0500] pkgacct using '/usr/bin/gzip -6' to compress archives
[2014-07-29 10:41:03 -0500] pkgacct working dir : /backup/2014-07-29/accounts/functest01
[2014-07-29 10:41:03 -0500] Copying Reseller Config...[2014-07-29 10:41:03 -0500] Done
[2014-07-29 10:41:03 -0500] Copying Suspension Info (if needed)...[2014-07-29 10:41:03 -0500] Done
[2014-07-29 10:41:03 -0500] Copying SSL certificates, CSRs, and keys...[2014-07-29 10:41:03 -0500] Done
[2014-07-29 10:41:03 -0500] Copying Domain Keys....[2014-07-29 10:41:03 -0500] Done
"""
We are expecting to merge this into 11.46 shortly.
We shopped around the timestamp format, and this was unanimously preferred:
"""
[2014-07-29 10:41:03 -0500] pkgacct started.
[2014-07-29 10:41:03 -0500] pkgacct version 10 - user : functest01 - tarball: 1 - target mysql : default - split: 0 - incremental: 0 - homedir: 1 - archive version: 3 - running with uid 0
[2014-07-29 10:41:03 -0500] pkgacct using '/usr/bin/gzip -6' to compress archives
[2014-07-29 10:41:03 -0500] pkgacct working dir : /backup/2014-07-29/accounts/functest01
[2014-07-29 10:41:03 -0500] Copying Reseller Config...[2014-07-29 10:41:03 -0500] Done
[2014-07-29 10:41:03 -0500] Copying Suspension Info (if needed)...[2014-07-29 10:41:03 -0500] Done
[2014-07-29 10:41:03 -0500] Copying SSL certificates, CSRs, and keys...[2014-07-29 10:41:03 -0500] Done
[2014-07-29 10:41:03 -0500] Copying Domain Keys....[2014-07-29 10:41:03 -0500] Done
"""
We are expecting to merge this into 11.46 shortly.
Excellent. I second this!
Excellent. I second this!
In cPanel & WHM version 11.46.1 and newer logs created by the new backup system are more verbose, and have time stamps in the form of YYYY-MM-DD HH:MM:SS
In cPanel & WHM version 11.46.1 and newer logs created by the new backup system are more verbose, and have time stamps in the form of YYYY-MM-DD HH:MM:SS
Replies have been locked on this page!