Scalix Forums

Posted: **Fri Jan 13, 2006 4:33 pm**

cannot access SAC after changing hostname.

I followed the info from admin guide and followed the sticky note on fedora about setclasspath.sh.

this is what i get from the log when I start Tomcat.
Note: it shows my old domain name. (test.domain.com)

2006-01-13 15:23:41,875 INFO [SOAPDispatcherServlet.init:76] ====> CAA is starting up, standby <====
2006-01-13 15:23:41,957 WARN [CAAConfigLoader.parseConfigDocument:224] No services are configured in this config file
2006-01-13 15:23:41,967 ERROR [CAAConfigLoader.parseComponentNode:244] Service scalix.res, Component disabled has no class defined!
2006-01-13 15:23:42,036 INFO [GuidToServerCache$CleanupThread.run:39] Guid2Server cache is empty. Skipping cleanup
2006-01-13 15:23:42,042 FATAL [CAAInitializerManager.loadAllInitializers:58] Exception in initializer for scalix.res
java.net.UnknownHostException: test.domain.com: test.domain.com
at java.net.InetAddress.getLocalHost(InetAddress.java:1191)
at com.scalix.sac.ubermgr.caa.RESInitializer.initNotificationListener(RESInitializer.java:190)
at com.scalix.sac.ubermgr.caa.RESInitializer.init(RESInitializer.java:65)
at com.scalix.caa.framework.CAAInitializerManager.loadAllInitializers(CAAInitializerManager.java:52)
at com.scalix.caa.soap.SOAPDispatcherServlet.init(SOAPDispatcherServlet.java:114)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1029)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:862)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4013)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4357)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:823)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:595)
at org.apache.catalina.core.StandardHostDeployer.addChild(StandardHostDeployer.java:903)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:216)
at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:256)
at org.apache.commons.digester.Rule.end(Rule.java:276)
at org.apache.commons.digester.Digester.endElement(Digester.java:1058)
at org.apache.catalina.util.CatalinaDigester.endElement(CatalinaDigester.java:76)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.commons.digester.Digester.parse(Digester.java:1567)
at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:488)
at org.apache.catalina.core.StandardHost.install(StandardHost.java:863)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:483)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:427)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:983)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:349)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1091)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:789)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478)
at org.apache.catalina.core.StandardService.start(StandardService.java:480)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:2313)
at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:287)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
2006-01-13 15:23:42,050 INFO [SOAPDispatcherServlet.init:118] ====> CAA started, you may fire when ready <====

Posted: **Fri Jan 13, 2006 6:36 pm**

When you change your server's FQDN, you need to run sxmodfqdn with the syntax:

Code: Select all

sxmodfqdn -o old-hostname.domain -n new-hostname.domain

where old-hostname.domain is your old FQDN and new-hostname.domain is your new FQDN.

To be on the safe side you can also clear your SAC cache by going into your tomcat-home/work/Catalina/localhost subdirectory and remove the caa and sac subdirectory, then stop and restart the tomcat server. So, for example:

Code: Select all

cd /var/opt/jakarta-tomcat-5.0.28/work/Catalina/localhost
rm -rf caa
rm -rf sac
cd ../../../bin
./shutdown.sh
./startup.sh

Thanks,
Rachel

Posted: **Thu Feb 09, 2006 10:29 pm**

I had the same issue, even after I changed all the files mentioned in the manual under "Updating Scalix After Changing the Name of the Server" and running the above command.
I managed to get it working again by re-running the setup and choosing reconfigure.

Posted: **Thu Feb 09, 2006 10:37 pm**

Seems I was too fast. I am able to log into sac now, but not into webmail. Furthermore the mail node shown in sac has still the old name. I can create a new one, but I don't know how to move my users. Running 9.2.2 eval.

I will reinstall now, because I'm just testing anyway.

Posted: **Sat Feb 11, 2006 3:34 am**

For webmail to work again, you'll need to change your /etc/opt/scalix/webmail/partner.xml config file and restart tomcat; this contains references to your hostname. You might also want to check /var/opt/scalix/sys/smptd.cfg, but it depends on your DNS situation if this is relevant.

You don't need to change your mailnode - the mailnode is a logical structure and even though the default mailnode name is generated from the hostname (because in a mult-server-situation, each server has to have a different mailnode name for mail routing reasons), it does not have to match. Yet, if you want to change it, the way to do that would be to create a new mailnode using omaddmn, then "rename" all users (i.e. move them to the new mailnode) using a command similar to

Code: Select all

ommodu -o "Florian Scalix/old,mailnode" -n "Florian Scalix/new,mailnode"

The same would need to be done for the PDLs using the ommodpdl command; after that, the default mailnode can be reset using ommodmn -t and the old mailnode can be deleted.

You will then want to add the following line to you /var/opt/scalix/sys/general.cfg:

Code: Select all

SR_RESOLVE_MASK=4

and restart the Service Router. This is because the mailnode is part of the internal sender X.400 addresses and unless you tell the router to resolve the user name in the directory, ignoring the mailnode, old internal email would not be repliable.

Hope this helps,
Florian.