Menu

#531 opensipsdbctl with dbtext creates bogus data in version file

1.8.x
closed
None
5
2012-06-06
2012-06-05
No

On 1.8.X (not tested with svn trunk, just the latest svn 1.8 branch), if you use the opensipsdbctl tool to generate dbtext table files, the version table file has some bad data in it that causes opensips not to start:

dr_groups:2
id(int,auto) gwlist(string) description(string) <<----
dr_rules:3

It looks like this is some bad leftovers from drouting changes.

More importantly (and might be another bug report, I don't know), this error, when starting opensips, causes it to not log anything (to stderr, to log file, even with running the binary and the extra debug flags on the command line). This sucks because it took me forever to find out why startup was griping.

After I removed the bogus entry and started, logs were generated through my syslog facility, so i'm pretty sure logging is set up correctly (also this is a migrated 1.7.2 box, and logging was working fine on that).

Discussion

  • Razvan Crainea

    Razvan Crainea - 2012-06-05
    • assigned_to: nobody --> razvancrainea
     
  • Razvan Crainea

    Razvan Crainea - 2012-06-05

    Hi, Robert!

    Yes, this is indeed a bug which was only fixed on the svn trunk. I have just backported it to 1.8.
    Regarding the lack of messages in the syslog, my guess is that OpenSIPS was not even started because of those errors, and that's why you don't see the logs at syslog.
    Please get the latest svn sources/tarball of 1.8 and try to see if the problem still appears.

    Regards,
    Răzvan

     
  • Robert Smith

    Robert Smith - 2012-06-06

    >> Regarding the lack of messages in the syslog, my guess is that OpenSIPS was
    >> not even started because of those errors, and that's why you don't see the
    >> logs at syslog.

    While I agree this is the reason, having a bug in a datasource cause the entire init to tank out and not log *anything* is a categorically bad, bad, bad idea. I only say this because it's the first time since 1.6 that I've had an issue with startup not logging that caused me tremendous pain to track down because I had *nothing* to go on.

    With 1.8 i've experienced several issues with startup failure not logging anything out, has anything around this mechanism changed since this minor version release?

     
  • Robert Smith

    Robert Smith - 2012-06-06

    And thanks, indeed updating to trunk removed the dbtext generation problem.

     
  • Razvan Crainea

    Razvan Crainea - 2012-06-06

    Hi again!

    Although nothing has changed to the logging mechanism, I am not sure why you are experiencing such problems. I will try to reproduce this on my system and see what is happening.
    Till then I consider this bug closed, thanks for pointing it out.

    Regards,
    Răzvan

     
  • Razvan Crainea

    Razvan Crainea - 2012-06-06
    • status: open --> closed
     

Log in to post a comment.