Schedulers are disabled on reboot

[Damien Raemy]

Hello,

I developped a module to manage warranties. Every warranty has a validity period.

Every night, all the warranties must be scanned, and the system send e-mails if warranties are expired.

To do that, I created a function in an object that is called by a trigger. This trigger is set to run every night at 02:00. It normally works, but sometimes, the server is automatically shuted down to be saved (that's a virtual machine). It appens arount 01:00. When it appens, the scheduler doesn't work, and we must wait about the first connexion to the database to receive e-mail (thanks to field repeat missed).

The server is a Ubuntu 10.04 LTS Server.

[Damien Raemy (damien.raemy)]

Hello,

Any news of this bugfix? This bug disrupts our warranties management process.

Thanks.

[Damien Raemy (damien.raemy)]

Hello,

Does something have look at this bug? This is important for all nightly tasks. If schedulers are disabled every reboot, they are not trustworthy and we cannot use it.

Thanks.

[Christophe CHAUVET (christophe-chauvet)]

Hi

It's not a bug, you must indication in the configuration file (or on the command line) which database you want t start, separated with a comma

Regards

[Damien Raemy (damien.raemy)]

In which configuration file, please ?

[Damien Raemy (damien.raemy)]

I tested. It looks to function. But the bug is not resolved, because it limits the use of a server to only one database. If you have more than one database, you cannot setup all in the configuration file.

[Christophe CHAUVET (christophe-chauvet)]

No you can specify more than one database in the configuration file, separate each name by a comma.

It's not a bug, it's a feature !

[Damien Raemy (damien.raemy)]

Ok, thanks for your help. I think it's a little bit complicate, because you have to add the database name whenever you create a new database. It would be simplier if the schedulers are created automatically.

[Damien Raemy (damien.raemy)]

Hello,

I recently had problem with this bug (yes, this is a bug): I removed a test database. The, the server didn't start. I lost lots of time to find why: it was becaus the test database name was set in the startup script. If the schedulers wasn't disabled on reboot, this type of case would not happen.

[Vo Minh Thu (thu)]

Damien,

This is a choice we have made conscientiously. If a database has to be loaded by the server, that database must be specified on the command-line or in the configuration. (The database is also loaded automatically if someone try to access it via XML-RPC).

The reason for this behavior is simple: Imagine launching the server with a lot of different databases. In such a situation, loading all database even if you perfectly know you will work with only one would be clearly wrong.

[Damien Raemy (damien.raemy)]

Vo Minh Thu,

Lots of companies have some jobs that must turn during the night. And lots of this companies cuts services or virtual machines nightly to do backups. If you have to edit the script everytime you create, delete or rename a database, it becomes unmanageable.

It would be an option to give to the script (an argument) to tell we want to load all databases in the script.

[Vo Minh Thu (thu)]

It might be nice to provide a mechanism to inspect and discover 'active' databases.