Error Lockfile /var/run/rsnapshot.pid Exists
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top rsnapshot schedule overlapping, help with backup schedule up vote 0 down vote favorite I have to following configuration. rsnapshot.conf interval halfhourly 4 interval hourly 6 interval twohourly 12 interval daily 7 interval weekly 4 crontab 0,30 * * * * /usr/bin/rsnapshot halfhourly >> /var/log/rsnapshot.halfhourly.log 2>&1 5 * * * * /usr/bin/rsnapshot hourly >> /var/log/rsnapshot.hourly.log 2>&1 10 */2 * * * /usr/bin/rsnapshot twohourly >> /var/log/rsnapshot.twohourly.log 2>&1 15 3 * * * /usr/bin/rsnapshot daily >> /var/log/rsnapshot.daily.log 2>&1 20 6 * * MON /usr/bin/rsnapshot weekly >> /var/log/rsnapshot.weekly.log 2>&1 Only halfhourly is running correctly now. hourly spits out this error: rsnapshot encountered an error! The program was invoked with these options: /usr/bin/rsnapshot hourly ---------------------------------------------------------------------------- ERROR: Lockfile /var/run/rsnapshot.pid exists and so does its process, can not continue To me it seems like my 5 min space between halfhourly and hourly is too small. Is this configuration crazy? I like having backups every thirty minutes, that will probably save my ass some day. Please help me make a decent backup schedule, that doesn't clog up the system, but creates frequent enough backups. Thank you. backup rsnapshot share|improve this question asked Jan 12 '11 at 16:15 Znarkus 6021028 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote accep
instructions: Windows Mac Red Hat Linux Ubuntu Click URL instructions: Right-click on ad, choose "Copy Link", then paste here → (This may not be possible with some types of ads) More information about our ad policies X You seem to have CSS turned off. Please don't fill out this field. You seem to have CSS turned off. Please don't fill out this field. Briefly describe the problem (required): Upload http://serverfault.com/questions/221642/rsnapshot-schedule-overlapping-help-with-backup-schedule screenshot of ad (required): Select a file, or drag & drop file here. ✔ ✘ Please provide the ad click URL, if possible: Home Browse rsnapshot Mailing Lists rsnapshot Brought to you by: bebehei, djk20, drhyde, hashproduct, scubaninja Summary Files Reviews Support Mailing Lists rsnapshot-announce rsnapshot-cvs rsnapshot-discuss rsnapshot-maintainers rsnapshot-travis Re: [rsnapshot-discuss] lockfile https://sourceforge.net/p/rsnapshot/mailman/message/8208255/ problem and corrupted file problem Re: [rsnapshot-discuss] lockfile problem and corrupted file problem From: Helmut Hullen here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow http://stackoverflow.com/questions/19537893/removing-stale-lockfile-rsnapshot-doesn%C2%B4t-like-my-lock-files the company Business Learn more about hiring developers or posting ads with us Stack Overflow https://linux.die.net/man/1/rsnapshot Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Removing stale lockfile - rsnapshot doesn´t like my lock files up vote 1 down vote favorite I have error lockfile to pause rsnapshot from running some backups some times, so I created a lockfile for this time: cat > /var/run/rsnapshot/rsnapshot.pid << EOF $$ EOF sleep 120s But rsnapshot tells me "removing stale lockfile" and goes on with its backup. What do I have to do that the lockfile isn´t stale for rsnapshot ? The man tells this: If a lockfile exists when rsnapshot starts, it will try to read the file and stop error lockfile /var/run/rsnapshot.pid with an error if it can't. If it can read the file, it sees if a process exists with the PID noted in the file. If it does, rsnapshot stops with an error message. If there is no process with that PID, then we assume that the lockfile is stale and ignore it unless stop_on_stale_lockfile is set to 1 in which case we stop. That would mean, it shouldn´t be stale as long as the bashscript runs. But it doesn´t work this way. Edit: Damn, I found the problem, there is a problem if the lockfile is owned by another user than rsnapshot runs from... bash backup lockfile share|improve this question edited Oct 23 '13 at 9:38 asked Oct 23 '13 at 9:26 user2693017 48331128 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote Damn, I found the problem, there is a problem if the lockfile is owned by another user than rsnapshot runs from... share|improve this answer answered Oct 23 '13 at 11:12 user2693017 48331128 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By post local and remote filesystems for any number of machines. Local filesystem snapshots are handled with rsync(1). Secure remote connections are handled with rsync over ssh(1), while anonymous rsync connections simply use an rsync server. Both remote and local transfers depend on rsync. rsnapshot saves much more disk space than you might imagine. The amount of space required is roughly the size of one full backup, plus a copy of each additional file that is changed. rsnapshot makes extensive use of hard links, so if the file doesn't change, the next snapshot is simply a hard link to the exact same file. rsnapshot will typically be invoked as root by a cron job, or series of cron jobs. It is possible, however, to run as any arbitrary user with an alternate configuration file. All important options are specified in a configuration file, which is located by default at /etc/rsnapshot.conf. An alternate file can be specified on the command line. There are also additional options which can be passed on the command line. The command line options are as follows: -v verbose, show shell commands being executed -t test, show shell commands that would be executed -c path to alternate config file -x one filesystem, don't cross partitions within each backup point -q quiet, suppress non-fatal warnings -V same as -v, but with more detail -D a firehose of diagnostic information Configuration /etc/rsnapshot.conf is the default configuration file. All parameters in this file must be separated by tabs. /etc/rsnapshot.conf.default can be used as a reference. It is recommended that you copy /etc/rsnapshot.conf.default to /etc/rsnapshot.conf, and then modify /etc/rsnapshot.conf to suit your needs. Long lines may be split over several lines. "Continuation" lines must begin with a space or a tab character. Continuation lines will have all leading and trailing whitespace stripped off, and then be appended with an intervening tab character to the previous line when the configuation file is parsed. Here is a list of allowed parameters: config_version Config file version (required). Default is 1.2 snapshot_root Local filesystem path to save all snapshots include_conf Include ano