1. Forum
  2. Usenet
  3. COMP.DATABASES.IBM-DB2

  • DB2-Express C 11.1 on Ubuntu 16.04 - bitten by logind updates?

    From Joachim Tuchel@21:1/5 to All on Thu Jun 7 01:14:59 2018
    Dear group,

    for months since we upgraded our systems from Ubuntu 14.04 to 16.04 we've had DB2 stability problems.

    The client applications would get Errors that state the DBM is not running or the DBM is not able to process any requests and such. Soem applications would continue working at the very same time while others would see these problems.
    Restarting the Appications (but not the DBM) would solve the problem temporarily. This would happen two or three times a week, but not every day on our server systems

    I ran across this bug report at https://www.ibm.com/support/knowledgecenter/SS5R93_5.2.13/com.ibm.spectrum.sc.doc/fqz0_r_tbs_db2_rhel72.html

    and thought this would be worth a try, what could I loose? Why not add RemoveIPS=no to the logind conf?

    The server has now been running for a few days without any Problems of the kind described aboove. So my hopes are the change is the reason.

    can anybody confirm this RemoveIPC thingie is relevant on Ubuntu? has anybody else tried this?

    Joachim

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joachim Tuchel@21:1/5 to All on Sun Jun 10 01:51:52 2018
    So even if this posting didn't find much of an audience yet, it may be of interest to people that it seems like this change in logind settings has improved stability of our DB2 server on Ubuntu a lot. So I guess it is safe to say that you should put the
    line

    RemoveIPC=no

    into your logind .conf on Ubuntu (at least since 16.04).


    Maybe this will be of help to other users.

    Joachim



    Am Donnerstag, 7. Juni 2018 10:15:01 UTC+2 schrieb Joachim Tuchel:
    Dear group,

    for months since we upgraded our systems from Ubuntu 14.04 to 16.04 we've had DB2 stability problems.

    The client applications would get Errors that state the DBM is not running or the DBM is not able to process any requests and such. Soem applications would continue working at the very same time while others would see these problems.
    Restarting the Appications (but not the DBM) would solve the problem temporarily. This would happen two or three times a week, but not every day on our server systems

    I ran across this bug report at https://www.ibm.com/support/knowledgecenter/SS5R93_5.2.13/com.ibm.spectrum.sc.doc/fqz0_r_tbs_db2_rhel72.html

    and thought this would be worth a try, what could I loose? Why not add RemoveIPS=no to the logind conf?

    The server has now been running for a few days without any Problems of the kind described aboove. So my hopes are the change is the reason.

    can anybody confirm this RemoveIPC thingie is relevant on Ubuntu? has anybody else tried this?

    Joachim

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)