Messaging Server Install Problem
Hi All,
I am trying to install Messaging server from JES2005Q1 on Solaris 10. I installed the followings;
Directory server,
admin server,
access manager,
web server,
messaging server
with Configure later option. After the installation, I got directory server, admin server and web server running. Then, I started configuring access manager and delegated administration. "amconfig -s <file-name>" worked fine during the access manager configuration. After that, I ran "config_commda", which completed successfully. then, I restarted the web services, and tried to issue "commadmin" like the following:
# ./commadmin domain modify -S mail -H <fqhn>
Enter login ID: admin
Enter login password: <password>
Connection refused
Invalid value for Identity server host name: <fqhn>
Invalid value for Identity server port: 58088
Enter Identity server port[58088]:
This always produced the same result when I tried to use amadmin user as well, and failed all the time. I also tried to connect to /amconsole web page in vain, and got the following in the web server error log:
[02/May/2006:09:49:42] warning ( 783): for host <IP-address> trying to GET /amconsole/base/AMAdminFrame, service-j2ee reports: StandardWrapperValve[AMBaseServlet]: Servlet AMBaseServlet is currently unavailable
When I tried to connect to /da/DA/Login web page, I got the following exception in the web server error log:
[02/May/2006:10:46:31] info ( 783): CORE3282: stdout: java.net.ConnectException: Connection refused
I already checked that the directory server is up and running, and I was able to see the contents via a third party ldap browser using "cn=Directory Manager".
Any idea what might have gone wrong?
Thanks
[1851 byte] By [
rami] at [2007-11-26 6:56:00]
# 1
At whitch step did you runcomms_dssetup.pl?It needs to be run immediately after configuring Access Manager.Also, why are you installing 2005Q1, now, when 2005Q4 us the current product?
# 2
here is the exact steps that I followed:
1) Installed directory, messaging, web server and identity server with configure later option
2) configured web server to listen on 8088 with the admin port of 8888
3) ran "directoryserver configure" with default values
4) ran "mpsadmserver configure" with port 390 as admin port
5) ran "perl comm_dssetup.pl" with specifying Schema 2
6) disabled sendmail daemon
7) prepared amsamplesilent.my configuration file with access manager port number 58088 and two different paswords for both amadmin and amldapuser as specified in the manual
8) ran "amconfig -s amsamplesilent.my"
9) ran "config_commda" during which I supplied 58088 as access manager port number, 8088 as http port number, and "admin" as top level domain administrator
10) tried to run commadmin with the following failure:
# ./commadmin domain modify -S mail -H <fqhn>
Enter login ID: admin
Enter login password: <password>
Connection refused
Invalid value for Identity server host name: <fqhn>
Invalid value for Identity server port: 58088
Enter Identity server port[58088]:
By the way, since I have the setup CDs of 2005Q1 version, I am using it. Otherwise, there is no specific reason.
Thanks,
rami at 2007-7-6 15:29:30 >
# 3
> here is the exact steps that I followed:
>
> 1) Installed directory, messaging, web server and
> identity server with configure later option
ok
>
> 2) configured web server to listen on 8088 with the
> admin port of 8888
ok
>
> 3) ran "directoryserver configure" with default
> values
ok
>
> 4) ran "mpsadmserver configure" with port 390 as
> admin port
ok
>
> 5) ran "perl comm_dssetup.pl" with specifying Schema
> 2
This should have failed, as it requires Access Manager to be installed.
>
> 6) disabled sendmail daemon
ok
>
> 7) prepared amsamplesilent.my configuration file with
> access manager port number 58088 and two different
> paswords for both amadmin and amldapuser as specified
> in the manual
Where did 58088 come from? Should have been the same http port that you specified....
>
> 8) ran "amconfig -s amsamplesilent.my"
>
> 9) ran "config_commda" during which I supplied 58088
> as access manager port number, 8088 as http port
> number, and "admin" as top level domain
> administrator
Again, if your web server isn't listening on 58088, none of this is going to work.
>
> 10) tried to run commadmin with the following
> failure:
>
> # ./commadmin domain modify -S mail -H <fqhn>
> Enter login ID: admin
> Enter login password: <password>
> Connection refused
> Invalid value for Identity server host name: <fqhn>
> Invalid value for Identity server port: 58088
> Enter Identity server port[58088]:
>
> By the way, since I have the setup CDs of 2005Q1
> version, I am using it. Otherwise, there is no
> specific reason.
I would dump those cd's, and download/make a new set.........
There have been lots of bug fixes with 2005Q4 (aka JES4)
>
> Thanks,
# 4
I did the the steps in the order of your suggestion:
1) ran the "amconfig" specifiying 8088 as port number, on which the https server is configured to listen to
2) ran the "comm_dssetup.pl"
3) ran "config_commda" giving the 8088 as the port numbers of access manager and http server
4) ran the following commadmin, which failed again:
# ./commadmin domain modify -S mail -H <fqhn>
Enter login ID: amadmin
Enter login password: <password>
Invalid value for login ID: amadmin
Invalid value for login password
Invalid value for login domain: <domain name>
Enter login ID[amadmin]
I tried to use both "amadmin" and "admin" with no luck.
5) I also noticed the following when I tried to restart the web server:
failure: WebModule[/amserver]: WEB2783: Servlet /amserver threw load() exception
javax.servlet.ServletException: WEB2778: Servlet.init() for servlet LoginLogoutMapping threw exception
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:949)
...
Any suggestions?
Thanks,
rami at 2007-7-6 15:29:30 >
# 5
1) ran the "amconfig" specifiying 8088 as port number, on which the https server is configured to listen to
Why "https"? That may be a problem, especially if you don't have a certificate.
as to your error message:
t LoginLogoutMapping threw exception
I've seen that before, and it's usually caused by
we have seen error whenever the AM doesn't find itself in the plattform list. Then you have to update this list; to do this, create an xml-request-file (let's say 'modify_plattform_service.xml') similiar to:
--> snip <--
<?xml version="1.0" encoding="ISO-8859-1"?>
<!--
Copyright (c) 2004 Sun Microsystems, Inc. All rights reserved
Use is subject to license terms.
-->
<!DOCTYPE Requests
PUBLIC "-//iPlanet//Sun Java System Identity Server 2004Q2 Admin CLI DTD//EN"
"jar://com/iplanet/am/admin/cli/amAdmin.dtd"
>
<!-- CREATE REQUESTS -->
<Requests>
<SchemaRequests serviceName="iPlanetAMPlatformService" SchemaType="Global">
<ModifyDefaultValues>
<AttributeValuePair>
<Attribute name="iplanet-am-platform-server-list" />
<Value>http://am001.yourdomain.com:80|01</Value>
<Value>http://am002.yourdomain.com:80|02</Value>
<Value>https://am001.yourdomain.com:443|03</Value>
<Value>https://am002.yourdomain.com:443|04</Value>
</AttributeValuePair>
<AttributeValuePair>
<Attribute name="iplanet-am-platform-cookie-domains" />
<Value>.yourdomain.com</Value>
<Value>.your-external-domain.com</Value>
</AttributeValuePair>
</ModifyDefaultValues>
</SchemaRequests>
</Requests>
--> snap <--
and run
amadmin -t modify_platform_service.xml
Furthermore you may want to extend the DNS-alias list similar to:
--> snip <--
dn: ou=services,@ldap.rootsuffix@
changetype: modify
replace: sunxmlkeyvalue
sunxmlkeyvalue: sunidentityrepositoryservice-sunOrganizationAliases=am001.yourdomain.com
sunxmlkeyvalue: sunidentityrepositoryservice-sunOrganizationAliases=am002.yourdmomain.com
sunxmlkeyvalue: sunidentityrepositoryservice-sunOrganizationAliases=am.your-external-domain.com
-
replace: sunkeyvalue
sunkeyvalue: sunidentityrepositoryservice-sunOrganizationStatus=Active
dn: @ldap.rootsuffix@
changetype: modify
replace: objectClass
objectClass: sunISManagedOrganization
objectClass: sunNameSpace
objectClass: top
objectClass: sunManagedOrganization
objectClass: organization
-
replace: sunOrganizationAlias
sunOrganizationAlias: am001.yourdomain.com
sunOrganizationAlias: am002.yourdomain.com
sunOrganizationAlias: am.your-external-domain.com
--> snap <--
# 6
I updated the xml file according to our domain name and port number, and tried to run amadmin with the follwoing failure message;
lithium# ./amadmin -t sug.xml -u amadmin -w <password>
Error 10: Cannot process requests:
Data validation failed for the attribute iplanet-am-platform-server-list
By the way, in my previous message everything should be "http", there is no "https" configured so far. It was just a typo, sorry.
Thanks,
rami at 2007-7-6 15:29:30 >
# 7
Hm. My steps say:It' appears to be complaning about an attribute in your sug.xml file.You need to fix that....
# 8
I did run the amadmin successfully after correcting the xml file:
# ./amadmin -t sug.xml -u amadmin -w <password>
Success 0: Successfully completed.
However, I still get the following error when I start the web server:
l# ./start
Sun ONE Web Server 6.1SP4 B12/16/2004 11:42
info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_01] from [Sun Microsystems Inc.]
info: WEB0100: Loading web module in virtual server [https-<fqhn>] at [/amconsole]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [https-<fqhn>] at [/amserver]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [https-<fqhn>] at [/ampassword]
warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
info: WEB0100: Loading web module in virtual server [https-<fqhn>] at [/amcommon]
info: WEB0100: Loading web module in virtual server [https-<fqhn>] at [/da]
info: WEB0100: Loading web module in virtual server [https-<fqhn>] at [/commcli]
info: WEB0100: Loading web module in virtual server [https-<fqhn>] at [/search]
failure: WebModule[/amserver]: WEB2783: Servlet /amserver threw load() exception
javax.servlet.ServletException: WEB2778: Servlet.init() for servlet LoginLogoutMapping threw exception
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:949)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:347 8)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
-- Root Cause --
java.lang.ExceptionInInitializerError
at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.j ava:71)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:347 8)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
Caused by: java.lang.NullPointerException
at com.sun.identity.common.FQDNUtils.<init>(FQDNUtils.java:71)
at com.sun.identity.authentication.service.AuthD.<clinit>(AuthD.java:165)
... 14 more
info: HTTP3072: [LS ls1] http://<fqhn>:8088 ready to accept requests
startup: server started successfully
If you still think that I should extend the DNS-alias as suggested in your previous replies, could you send some info how to do that? Or any other suggestions?
Thanks!
rami at 2007-7-6 15:29:30 >
# 9
I suspect that something you entered during the configuration step was incorrect, and possibly removal of all the packages, and a start from scratch, again.I installed all these same pieces, and had no problems at all.
# 10
Before starting from scratch, I would like to go back to my original problem. The only thing I want to have is to Java Messaging server with a gui interface to be able to manage user accounts. I have been using the old version (version 4.2 from Netscape) with just three components: Directory server, messaging server, and admin server. I was able to use ldap console to manage my users and domains with that old version.
So, my original question is what to do to get the same thing with the latest Java messaging server? As I said, I just need messaging server with an appropriate management gui. The story begins like that; I first started installing those three components (directory server, messaging server, and admin server). Then, I noticed that I was not able to define mail specific details for a user through the ldap console as I used to do. When I create a user account, I check the "mail account" checkbox, but I do not get the "mail tab" on the create user account window. After that, I opened an issue with Sun, and they suggested me to use delegated admin tool, after which I started dealing with that all access manager and webserver thing. Otherwise, I am not interested in web server or access manager.
So, my simple question is what to install just to be able to use messaging server with an appropriate admin tool. I have been trying to use 2005Q1. Is it same thing with the latest 2005Q4, or is it possible to use ldap console for mail users administration in 2005Q4.
Thanks!
rami at 2007-7-6 15:29:30 >
# 11
The Directory Console is "deprecated". Means that the function is no longer there.
You cannot reliably create users that will funcction with current Messaging Servers.
The product has evolved quite a bit since the old Netscape days. It's much more complex, and the Directory entries are also more complex.
The products you have chosen are indeed the correct ones.
All I can suggest to you, is that you must have made some error during your configuration step, and that recovering from that may be more work than simply wiping the system, and starting over.
I have made exactly the same installation you have, myself. On Solaris 10. I had none of your issues, and my system is working well.Delegated Admin is able to create users and groups. I can use commadmin or DA's gui.....
# 12
Thanks for the explanation! I just want to make sure my steps are in the correct order before starting from scratch. Here is my plan;
1) Install Solaris 10
2) Install the following components from the JES setup CD with configure later option;
-Directory server
-messaging server
-web server
-identity server
3) Configure java web server using "/opt/SUNWsrv/setup/configure"
4) Configure directory server using "/usr/sbin/directoryserver configure"
5) Configure admin server using "/usr/sbin/mpsadmserver configure"
6) Edit amsamplesilent to prepare amsamplesilent.my
7) Configure Access Manager using "/opt/SUNWam/bin/amconfig -s amsamplesilent.my"
8) Run "/opt/SUNWcomds/sbin/comm_dssetup.pl" with Schema 2
9) Run "/opt/SUNWcomm/sbin/config_commda"
10) Restart the web server
11) Run "commadmin domain modify -S mail -H <fqhn>
12) Configure messaging server using "/opt/SUNWmsgsr/sbin/configure"
Does that order seem to be correct? Any suggestions?
Thanks!
rami at 2007-7-6 15:29:30 >
# 13
> Thanks for the explanation! I just want to make sure
> my steps are in the correct order before starting
> from scratch. Here is my plan;
>
> 1) Install Solaris 10
Yes. Personally, I do the full plus oem install.
>
> 2) Install the following components from the JES
> setup CD with configure later option;
> -Directory server
> -messaging server
> -web server
> -identity server
Please add Delegated Admin to your list
>
> 3) Configure java web server using
> "/opt/SUNWsrv/setup/configure"
I would change the order, actually.
I configured in this order:
1. Directory Server
1.5 admin server for above.
2. Web Server
3. Access Manager (interactive, not silent)
4. comm_dssetup.pl
5. Messaging Server
6. Delegated Admin
do your commadmin commands AFTER you install Messaging Server.
>
> 4) Configure directory server using
> "/usr/sbin/directoryserver configure"
>
> 5) Configure admin server using
> "/usr/sbin/mpsadmserver configure"
>
> 6) Edit amsamplesilent to prepare amsamplesilent.my
>
> 7) Configure Access Manager using
> "/opt/SUNWam/bin/amconfig -s amsamplesilent.my"
>
> 8) Run "/opt/SUNWcomds/sbin/comm_dssetup.pl" with
> Schema 2
>
> 9) Run "/opt/SUNWcomm/sbin/config_commda"
>
> 10) Restart the web server
>
> 11) Run "commadmin domain modify -S mail -H <fqhn>
>
> 12) Configure messaging server using
> "/opt/SUNWmsgsr/sbin/configure"
>
> Does that order seem to be correct? Any suggestions?
>
> Thanks!
# 14
I installed everything from scratch according to your suggestions. But I am still at the same place, I am getting the same error when I try to start web server as the following:
failure: WebModule[/amserver]: WEB2783: Servlet /amserver threw load() exception
javax.servlet.ServletException: WEB2778: Servlet.init() for servlet LoginLogoutMapping threw exception
I ran the access manager script that you suggested in one of the previous replies, but it did not make any difference.
You are saying that you follow the same steps and got it running. Which version are you using exactly, 2005Q1 or 2005Q4? Do I have to apply any patch to Solrais 10 before starting the JES installation?
Thanks!
rami at 2007-7-6 15:29:30 >
# 15
I forgot to say that the only thing that was failed during the install is the restart of the web server and running "commadmin domain modify".
Here are the last three steps that I did after all others;
1) config_commda
2) Restart of the web service, which was failed to load /amserver
3) Tried to run "commadmin domain modify -S mail -H <fqhn>", which did not do anything but kept asking me the login ID as the following:
# ./commadmin domain modify -S mail -H <fqhn>
Enter login ID: admin
Enter login password: <passwd>
Invalid value for login ID: admin
Invalid value for login password
Invalid value for login domain: <domain name>
Enter login ID[admin]:
ramia at 2007-7-21 15:04:17 >
# 16
Yes, I have successfully installed BOTh 2005Q1 and 2005Q4, following these exact instructions, with no problems.
I suspect that you may have answered one or more of the questions incorrectly.
If you cannot get beyond this, you may want to open a support case. It's very difficult to work through something this complex via posted notes......
I remember installing the current Solaris 10 patch setup, yes.
# 17
I had a similar problem, the reason was the ou=ClientData tree was missing.I have seen the failed request in LDAP access log.
# 18
missing LDAP entries should be taken care of by running comms-dssetup.pl against any/all ldap servers to be used.That's a requirement of the install.
# 19
Thank you! This helped me!
