Author Topic: ebackup module - Could not get lock for service  (Read 2503 times)

sbornman

  • Zen Apprentice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
ebackup module - Could not get lock for service
« on: June 12, 2012, 09:23:13 am »
Hi,

I have installed Zentyal 2.2-2, and it has been running for a while. It runs only basic services like DNS and File Sharing.
I wanted to configure the backups. First of all I tried to do the backups to a RSYNC compatible NAS device on the network, once I saved the configuration, the ebackup module wont start up anymore. Zentyal now keeps on telling me there are unsaved changes, but everytime I click on save the same thing happens again.

In the meantime I have changes the backup module config to backup to the local file system.

Here is some output when I try to manually restart the ebackup module:

 sudo /etc/init.d/zentyal ebackup start
 * Restarting Zentyal module: ebackup                                    [fail]
Could not get lock for service: ebackup

Here is some output of /var/log/zentyal/zentyal.log

2012/06/12 09:02:16 ERROR> Lock.pm:31 EBox::Util::Lock::lock - Could not get lock for service: ebackup

Please I need some advice, as I need to get these backups running.

Javier Amor Garcia

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1225
  • Karma: +12/-0
    • View Profile
Re: ebackup module - Could not get lock for service
« Reply #1 on: June 19, 2012, 02:41:27 pm »
Try this command to force lock removal:

sudo rm /var/lib/zentyal/tmp/ebackup.lock

sbornman

  • Zen Apprentice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: ebackup module - Could not get lock for service
« Reply #2 on: June 19, 2012, 06:35:36 pm »
Hi Javier,

That is one of the first things I tried to do.
After I removed the .lock file, it is still impossible to start/restart/stop the ebackup module.

This happened to me before when I tried to set up the backup method to "RSYNC".
I think I have initially entered the RSYNC server name incorrectly, but cannot fix this now, because the config now also does not save properly in the web interface. I always get the "some modules reported a problem" message now, and the cause is the ebackup module lock.