Yes.
I'm only testing from the outside now, but I guess its only a matter of routing if it doesn't work on the inside.
Moderator: ScalixSupport
Code: Select all
-Uninstalled Scalix (everything)
-Manually removed rpm's that wasn't removed by Scalix (e.g. JRE)
-Manually removed httpd and dependencies
-Made sure that all config for scalix and httpd was removed (updatedb is a nice tool..)
-Installed httpd with as simple configuration as possible
-Ensured everything worked
-Manually installed java from the Scalix package, and got rid of everything that was there before. -Since I had a Java issue at first place I checked everything around this issue before I continiued
-Installed Scalix, used default values all the way
Code: Select all
2006-07-10 17:40:26,856 INFO [RESNamedInstances.initNamedInstances:61] Loading Scalix named instances.
2006-07-10 17:40:26,874 INFO [RESNamedInstances.initNamedInstances:100] Finised reading Named Instances. Total Named instances in the global config file are = 1
2006-07-10 17:40:26,877 INFO [RESNamedInstances.initNamedInstances:101] Checking Named Instances state..
2006-07-10 17:40:26,889 DEBUG [CmdExecution.executeCmd:138] ENVIRONMENT: LANG=en_US.UTF-8 OM_CHAR=UTF-8
2006-07-10 17:40:26,892 DEBUG [CmdExecution.executeCmd:140] COMMAND: /opt/scalix/bin/sxchkinstances
2006-07-10 17:40:27,070 INFO [RESNotifier.startRegistrationThread:80] Launching Registration-thread
2006-07-10 17:40:27,439 DEBUG [RESDispatcherServlet.initialize:373] : Almost finished initialization, now waiting for registration
2006-07-10 17:40:27,564 ERROR [RegistrationEventPoller.run:75] NO Named instances located in the global config file. RES service may not be able to register it self
Code: Select all
/etc/init.d/scalix-tomcat stop
Code: Select all
/etc/init.d/scalix-tomcat start
Return to “Scalix Management Services”
Users browsing this forum: No registered users and 2 guests