zentyal not responding to commands

[cmdr]

Hello,

So it appears like sudo /etc/init.d/zentyal apache restart does not appear to be working, even when I try to restart the zentyal service it just stays there doing nothing.

sudo /etc/init.d/zentyal stop -- I see it in the process list (ps aux) but nothing happens.

All the other zentyal modules are working except the web interface to manage zentyal.  About the only other option I have is to reboot the server however we can't do that just now and we need the web interface up and running to manage users.

We are runnign zentyal 3.1 on ubuntu 12.04 LTS

All the other services appear to be working correctly however the administrative console does not come up.

The /var/zentyal/zentyal.log:

2014/10/17 02:17:01 ERROR> Lock.pm:35 EBox::Util::Lock::lock - Could not get lock for service: manageEBoxLogs
2014/10/17 03:17:01 ERROR> Lock.pm:35 EBox::Util::Lock::lock - Could not get lock for service: manageEBoxLogs
2014/10/17 04:17:01 ERROR> Lock.pm:35 EBox::Util::Lock::lock - Could not get lock for service: manageEBoxLogs
2014/10/17 05:17:02 ERROR> Lock.pm:35 EBox::Util::Lock::lock - Could not get lock for service: manageEBoxLogs
2014/10/17 06:17:02 ERROR> Lock.pm:35 EBox::Util::Lock::lock - Could not get lock for service: manageEBoxLogs
2014/10/17 07:17:01 ERROR> Lock.pm:35 EBox::Util::Lock::lock - Could not get lock for service: manageEBoxLogs

Any help is appreciate it.

Thanks,

[robb]

You are sure it is a 3.1 version? That is the beta version for 3.2...

[cmdr]

After looking at it closer I think it's 3.0,  Is there a way to find the version from the command line?

Thanks

[Zei]

Hello, you can find the lock files under /var/lib/zentyal/tmp/, so try to remove the .lock file (I suppose that could be something like manageEBoxLogs.lock), and afterwards you should be able to restart the apache service.

Cheers

[cmdr]

I have deleted the lock, when I run sudo /etc/init.d/zentyal apache status it says it's running.  When I try to stop it it does not stop it stays there waiting for something to happen.

Also, I believe the lock error is being caused by a cron job or something that is automated, I see it every hour on the hour.  The error is not being generated by me trying to stop and stop apache.

Thanks

[Zei]

I will advise to try to kill all apache processes and try to run it again. Also, you will probably have some restarting processes hanged, try to kill them too.