Error initializing streams driver!

HCL Domino Domino Forum
1

Hi all,

I’ve installed 6.0.1 on Solaris 9 and got some problems which are very strange and not documented anywhere.

The error shows when starting the server:

“ERROR INITIALIZING STREAMS DRIVER!!, It might not have not been installed on the system.”

And appears for the following processes:

IMAP, POP3, LDAP, SMTP.

HTTP runs just fine without any errors…

Anyone might have any idea what might be the cause? Sendmail or any other services are not running, so it’s not a conflicting ports issue…

Thanks,

Oded.

2

Subject: ERROR INITIALIZING STREAMS DRIVER!!

Domino 6 on Solaris uses a new driver to support the thread pool model of network IO. This model is used by all the servers you mentioned and is not used by the web server. The new driver is installed as part of the Sun OS if you are using the Sun OS required. Check the prerequisites for Domino 6.

Pete Mierswa

M&C Development

IBM

3

Subject: RE: ERROR INITIALIZING STREAMS DRIVER!!

Please contact Lotus Support so that you can get the help you need to resolve this problem.

4

Subject: RE: ERROR INITIALIZING STREAMS DRIVER!!

Hi Pete,I have been trying to figure out more information about that problem…

Out of 3 servers only one didn’t produce the above mentioned error…

Both of the problematic servers had the SAME configuration in terms of hardware and especially software as it was mirrored from the ONLY server that was not producing that error.

I would be great to get some more details of solving that issue, as the customer has already gave up the Solaris solution and is now considering a Windows 2000 Server configuration.

I don’t think that “Domino 6 on Windows 2000 Server” is a BAD solution, however, I expect that the solution will work across the platform and not be based on a “Trial and Error” installation, which not always work…

Thanks,

Oded.

5

Subject: RE: ERROR INITIALIZING STREAMS DRIVER!!

Hi Oded

We experienced the same problem when installing Domino R6.01 CF1 on a Solaris System with Veritas Cluster Software. On one system Domino installes and runs fine, but on the other node in the cluster we get the error message. By analysing the installation script we were able to get the sytem up and running. Here is what we did:

Excerpt from the Lotus Notes and Lotus Domino fix list:

SPR# TCAR4AMQLW - Fix the Solaris edition so it properly installs the streams driver on 64-bit systems. [5.0.1a]

There are two workarounds to this issue:

  1.    Reboot the machine.

or

  1.    If the OS is in 64-bit mode, after installing Domino, make sure /kernel/drv/nmux.conf and /kernel/drv/sparcv9/nmux exist, then as "root", run the following:

/usr/sbin/add_drv -v -m ‘* 0666 bin bin’ -i nmux nmux

Additionally, this error has been seen in more recent versions. The ‘ERROR INITIALIZING STREAMS DRIVER’ crash can also occur if the link in /dev to /devices/pseudo does not exist. In a normal installation of the 64-bit nmux driver, doing an ‘ls -l nmux’ in /dev should show this:

lrwxrwxrwx 1 root other 30 Feb 2 12:15 nmux → …/devices/pseudo/clone@0:nmux

If this link is not there, check to make sure that /devices/pseudo/clone@0:nmux exists. If it does, you can create the link in /dev by hand by logging in as ‘root’, and executing:

ln -s /devices/pseudo/clone@0:nmux /dev/nmux

After that we copied the following files from the running system to the non functioning node:

/usr/kernel/strmod/sparcv9/notify

/usr/kernel/strmod/notify

/usr/kernel/drv/sparcv9/listen

/usr/kernel/drv/listen.conf

/usr/kernel/drv/listen

After that the system started up perfectly. I still do not know if this is a supported approach, but it works for us. Could someone from IBM verify whether this is ok or not?

We are very happy with Domino on Solaris.

I hope my information helps, please contact me, if you need further information: tom.haab@advantix.ch

Greetings

Tom

6

Subject: Solution - ERROR INITIALIZING STREAMS DRIVER!!

We were expereincing this error at a Disaster Recovery test. We could connect to a mailfile using iNotes via port 80 but could not connect using the notes client.

The solution to the problem was to copy :

/usr/kernel/strmod/sparcv9/notify

/usr/kernel/strmod/notify

/usr/kernel/drv/sparcv9/listen

/usr/kernel/drv/listen.conf

/usr/kernel/drv/listen

To the new server AND make this link in /dev —

listen → /devices/pseudo/listen@0:listen

This fixed the listen error and all was good.

Hope someone finds this usefull!

Jerry