This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


Nov 26, 2015, 1:21 PM
2 Posts

IBM Traveler crashes on ubuntu

  • Category: Notes Traveler
  • Platform: Linux
  • Release: 9.0.1
  • Role: Administrator
  • Tags: Traveler Ubuntu
  • Replies: 2

Hi

We have several domino/traveler servers with that are running on Ubuntu Server OS. They have been stable for months. Last week one of them started crashing, and this week, another one started crashing with the exact same error / nsd.

The error message that is logged in the console.log is as follows:

traveler: wcsrtombs.c:99: __wcsrtombs: Assertion `data.__outbuf[-1] == '\0'' failed.
Stack base = 0xc5efefb4, Stack size = 14820 bytes
Fatal Error signal = 0x00000006 PID/TID = 3527/-974128320
11/26/2015 20:42:48  Running NSD
NSD is in progress .................

 

The first server was originally running on Ubuntu 12.04 LTS, but the problem followed us into a newly installed 14.04 LTS server as well. We then migrated to windows and the server is now running fine. We copied the NTSDB folder with us over to windows so don't believe there is any problems with these.

The second server was originally on 14.04 LTS. We tried to downgrade ubuntu packages that was recently updated (security updates only) and at first it looked promising but it started crashing again after about a day, and it now will crash/restart about every 10 minutes or so. We also tried running on the previous kernel version as we have experienced problems with this in the past.

We are on domino 9.01 FP4, with the 901FP4HF526 patch applied. Traveler is on 9.0.1.7.

The problem is definately with traveler, cause if we start the server without traveler, it will run fine.

Has anyone else seen/solved this, or does anyone have any suggestion? We know ubuntu is unsupported for this, but it's just a very convenient platform for us :-)

Thanks, really hope someone can help!

Nov 30, 2015, 11:45 PM
8 Posts
Kindly Open a PMR

Hi Stein,

Thank you for raising a detailed problem description on this.

You are right, Traveler is not supported to run on Ubuntu platform.

Although not supported, if you want to learn more on what is causing this issue, it will be best to open a PMR with IBM Support, so the necessary files can be analyzed.

link to our Electronic Service Request here: https://www-947.ibm.com/support/servicerequest/Home.action

You must be able to reproduce the same crash scenario though, so keep that in mind before you open the PMR.

Thanks!

Dec 1, 2015, 9:04 AM
20 Posts
RE
Hi Stein,

I think that there is some misunderstanding here. As per our policy we cannot troubleshoot unsupported configuration (Ubuntu) when all works fine on Windows. Especially while the issue is related to server stability.

Going back to your problem each time while the server crash NSD is generated along with panic/fatal thread. This is so we can review the failing functions. Panic stack (even if this is Traveler task) might contains OS, third party, or memory calls that are causing a server to crash. I suggest that you look for fatal/panic thread in the NSD. That might give you some clue on what function is causing the server to crash.

If you're not familiar with analyzing NSDs and finding the panic/fatal threads (you can use text editor to review the NSD ) I suggest that you use LND tool:
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Using_the_LND_tool_to_analyze_IBM_Lotus_Notes_and_Domino_hangs_and_crashes

As this is Ubuntu you might not see the threads in the NSD... I suspect that you see the following instead of threads:
The GNU debugger (gdb) is required to collect stack information.
Please install gdb under the directory /usr/bin and ensure the
Domino server id has permission to execute /usr/bin/gdb.

If thats the case then you need to install GNU debugger (gdb), recreate the crash and then look for panic/fatal thread to see what function is crashing the server.



This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal