Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dialplan: WARNING: a load command already generated, aborting reload... #510

Closed
ovidiusas opened this issue May 14, 2015 · 6 comments
Closed
Assignees
Labels

Comments

@ovidiusas
Copy link
Member

If the httpd module is loaded along with the dialplan and mi_fifo module, the following warning shows up.

WARNING:dialplan:dp_load_db: a load command already generated, aborting reload...

It looks like the dialplan data is loaded by the MI FIFO process and the warning is generated by the HTTPD process. This is reproducible in trunk and 2.1.

@razvancrainea razvancrainea self-assigned this May 15, 2015
@razvancrainea
Copy link
Member

Hi, Ovidiu!

Is the data actually loaded simultaneously from the two engines FIFO and HTTPD? How do you reproduce this?

Best regards,
Răzvan

@ovidiusas
Copy link
Member Author

It's happening at start up every single time.

@ovidiusas ovidiusas added the bug label May 15, 2015
@ionutrazvanionita
Copy link
Contributor

fa14431 && 6164d1c loads data in child_init and then closes the connection; in mi_child_init it is done only the connect part

@bogdan-iancu
Copy link
Member

@ovidiusas , could you test on your side and confirm the fix - so we can do the backport to 2.1 too.

@ovidiusas
Copy link
Member Author

It is working fine now: the db data is loaded by the first receiver process.
It would be nice if the the load could be distributed over the receivers in a round robin fashion: first module takes the first receiver, second module that loads a db takes the next receiver and so on.
It would improve the startup time is really big tables are cached into memory.

@bogdan-iancu
Copy link
Member

@ovidiusas, yes and no. YES: indeed it will make the startup faster ; NO: the whole idea is to avoid blocking the SIP processing while loading, so we need to be sure that some procs are still left untouched by the init and available for handling SIP traffic.
Please open a separate feature request on this topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants