Messaging 3.x fails to start with "Unable to initialize" error

Question

Messaging Server fails to start from the Admin Server or by using the "start" command.
<P>
# /etc/NscpMail start
Startup Problem:
Unable to initialize the environment from (/etc/netscape.mail.conf)
Netscape Messaging Server Exiting!
<P>
The Messaging Server log file will not show any entries.
<P>
The problem is most likely due to a missing dbswtich.conf
file or a zero byte file.
<P>
The default dbswitch.conf
file contains a single line:
<P>
directory default ldapdb:///usr/netscape/suitespot/userdb/ldap/config/lcache.conf/
<P>
Restore this file from a backup if possible.
<P>
Unlike Admin Server, Messaging Server will require the correct file to be
restored because it immediately looks for its postmaster entries in the LDAP
directory. If you cannot restore the file:
<OL>
<LI>Place a temporary entry into the
file.
<LI>Start the admin server.
<LI>Enter the correct values into Global Settings,
Configure Directory Service.
<LI>Attempt to start the Messaging Server again.
</OL>
<P>
Tracing utilities (e.g. truss in Solaris) can
help analyze problems where servers fail to start and return little or no
useful errors.
<P>
truss -f -o <trussfile> /etc/NscpMail start
<P>
grep dbswitch.conf <trussfile>.
<P>
This would usually show admin returning a ENOENT error or reading zero bytes of
data.

Answer 1

I assume when you say "mentioned solutions", those include:
- Generating xorg.conf with aticonfig --initial
- Blacklisting the radeon module
- Generating the fresh fglrx modules with catalyst_build_module all
Also, how've you set it up? AUR, graysky's repository or directly from AMD's website?
Last edited by clfarron4 (2014-09-15 12:16:09)