I have a fresh install of a virtual server with Ubuntu 14.04 64bit and a cubeSQLServer 64bit 5.0.1 on it. I have a new, valid company key for unlimited connections installed with it.
Everything seems to run fine and when I restart the server, then CubeSQL is autostarting fine, as expected.
But then, each morning at 2:30, the database server is shutting down. When I connect to it with cubeSQLAdmin, then I see only such message: “… 02:29:48 CubeSQL Server is shutting down”. (The Ubuntu Server is NOT restarted).
I couldn’t find any related messages in other log files, so far. Probably I am missing something…
Does anyone have an idea what might be going wrong here? Have you seen something like this before?
You could look in the kernel log and also the /var/log/messages, for entries right before the shotdown ocurred.
Also check root’s cron entries “sudo crontab -l” and the content of /etc/cron.daily.
Thanks Sascha! I already checked out messages, but could not find anything.
There are a some entries for a daily cron job at 2:16, so when my database goes down just 15 minutes later, then there might be a link to it. However, I am stuck with this - I guess i will need some help from our hosting provider.
I have an other vserver from them, which worked flawlessly for some years now, with cubesql. But now I don’t know whether this shutdown is linked to the new version of cubesql (5.0.1) or to the new version of Ubuntu Server I am using with it…
What I know is, that HostEurope (my provider), did just release these new vServers with Ubuntu 14.04 and Plesk and it is highly likely that they are just now running into issues they did not discover during their beta tests (if ever they did such a thing …)
I see you have plesk panel installed. Seems something related to some backup procedure. Maybe the backup procedure is shutting down the DB to unlock files and proceed. Check the backup management in your plesk panel, if it’s not available, consult your hosting, maybe they are doing this.
My guess is you are running on top of Parallels Virtuozzo. Plesk integrates nicely with this as both are from Parallels. In a typical hypervisor the host would not have access to shut down individual processes. They could send a shutdown to the VM and everything down but not individual processes. However Virtuozzo is really just lightweight containers and the host can see all of your data/processes. So perhaps like Rick said some backup job is seeing open files or something and shutting it down. I would recommend a KVM or Hyper-V based host as they typically do not oversell and you are more in control of your processes.
if it is the backup software that is shutting it down, excluding the cubeSQL files (data files) from the backup software. Have cubeSQL do its backups to another directory that is backed up.
At the moment HostEurope confirmed my issue and moved it to 2nd level support. My closest guess so far is what Phillip Zedalis is writing.
My hackish workaround for the moment is a cron job which restarts cubesql server. But if we can’t solve this in a clean way, I will have to change the provider.
I do have a second vServer with the same provider which is running flawlessly since 4 years, with CubeSQLServer and some Xojo Webapps. It is only with their latest version vServer (the combination of Ubuntu 14.04 and Plex is a very new release), where we experience these problems.
The hoster as well as Marco Bambini advised me to run the cron jobs manually and see what’s happening. I’ve been running all those cron jobs I found in /etc/cron.daily, /etc/cron.hourly, /etc/cron.d/
They did not report any errors, but CubeSQL is still running. So either the cron-jobs are not responsible for the regular shutdown (it happened again last night, at 2:30) - or something changed with todays automatic update of plesk-panel.
At the moment I am still stuck with the workaround of a script, which gets invoked by a cronjob every 2nd minute, in order to keep CubeSQL Server alive. For tonight I disabled all other cron jobs and I will see if cubesql is still going down (it was doing it again, last night).
For those interested, the script looks like this:
#!/bin/bash
if [[ ! `pidof -s cubesql` ]]; then
sudo cubesqlctl start
fi
Neither their support, nor their online forum, nor Marco Bambini did have an idea on how to solve this problem.
it is a pity, because I had CubeSQL running very stable for several years when using the older versions of HostEurope, Ubuntu and CubeSQL (Virtual Server Linux MAX 5.0, Ubuntu 10.04 and CubeSQL 4.3). Only Plesk is the same version 12.0.18 on both servers.
So Phillip Zedalis’ guess is probably the closest shot and I am going to withdraw from my contract with HostEurope now.
SQLabs’ Marco Bambini did send me a new beta version of CubeSQL Server (5.0.2) which seems to solve my issue of shutting down once every 24hours, on the latest vServers of hosteurope.com (ubuntu 14.04 with Plesk version 12).
CubeSQL has now survived the last night and I keep the test running another 24 hours, to see if it really works. But for now it looks promising.
[quote=182724:@Oliver Osswald]SQLabs’ Marco Bambini did send me a new beta version of CubeSQL Server (5.0.2) which seems to solve my issue of shutting down once every 24hours, on the latest vServers of hosteurope.com (ubuntu 14.04 with Plesk version 12).
CubeSQL has now survived the last night and I keep the test running another 24 hours, to see if it really works. But for now it looks promising.[/quote]
