Wieder ein RMI Problem auf dem Port 1099

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • asteini
    replied
    opps das eine Password hat mit dem anderen nichts zutun. :-)

      Leave a comment:

    • asteini
      replied
      Interessant : hab ich jetzt mal mittels (wie in /opt/open-xchange/etc/admindaemon/management.properties beschrieben)
      Code:
      perl -M'Digest::SHA1 qw(sha1_base64)' -e 'print sha1_base64("password")."=\n";'
      das meiner Meinung nach aktuelle Password generiert. Der Hash sieht anders aus als in der alten Konfig.

        Leave a comment:

      • asteini
        replied
        Hier wurde ein ähnliches Problem beschrieben.

        Error 404 | Page not found
        http://www.open-xchange.com/forum/showthread.php?5083-Installation-problem-SLES11SP1


        habe ebenfalls die mpasswd und das gehashte Pass geprüft. Stimmt mit der alten Konfig überein. Weiss den keiner einen Rat?

          Leave a comment:

        • asteini
          started a topic Wieder ein RMI Problem auf dem Port 1099

          Wieder ein RMI Problem auf dem Port 1099

          Hallo Leute ich brauche echt Hilfe. Muss hier ein Kunststück vollbringen. Wir haben die mysql Datenbanken eins zu eins auf einen neuen SLES11 Server migriert. Die OX Apliccations (Version6.18.2-20) SE natürlich auch neu aus den Repositories installiert. Zuvor OpenSuSE 11.1 OX Ver.6.18.1.
          Ohne "initconfigdb" und "registerserver" etc. haben wir die alte Datenbank praktisch wieder ans Laufen gebracht. Alle Einstellungen, Datenbankzugriffe haben wir händisch angepasst. Sodass alles funktioniert ... Userzugriffe etc..

          Was nicht funktioniert ist der Zugriff zur Datenabank über die Scripte unter "/opt/open-xchange/sbin"*. Beim Ausführen jeglicher Befehle kriegen wir einen:

          Code:
           
server could not be registered:
Error: Connection refused to host: localhost; nested exception is:
        java.net.ConnectException: Verbindungsaufbau abgelehnt
          Zuerst hatte wir die "localhost" unter Verdacht. Hat sich aber leider nicht bestätigt. Können auflösen, pingen, alles wunderbar. Mit netstat stellten wir fest der der RMI Port 1099 auf localhost nicht öffnet. Admindaemon gestartet und kriegen folgenden Fehler:

          Code:
          Feb 16, 2011 4:27:47 PM com.openexchange.groupware.userconfiguration.UserConfigurationStorageInit start
INFO: UserConfigurationStorage implementation: com.openexchange.groupware.userconfiguration.CachingUserConfigurationStorage
Feb 16, 2011 4:27:47 PM com.openexchange.event.impl.EventInit start
INFO: Parse Event properties
Feb 16, 2011 4:27:47 PM com.openexchange.event.impl.EventQueue init
INFO: Starting EventQueue
Feb 16, 2011 4:27:47 PM com.openexchange.event.impl.EventInit start
INFO: Adding Notification Listener
Feb 16, 2011 4:27:47 PM com.openexchange.event.impl.EventInit start
INFO: Adding LinkEventHandler
Feb 16, 2011 4:27:47 PM com.openexchange.event.impl.EventInit start
INFO: Adding AttachmentCleaner
Feb 16, 2011 4:27:47 PM com.openexchange.event.impl.EventInit start
INFO: Adding PropertiesCleaner
Feb 16, 2011 4:27:47 PM com.openexchange.event.impl.EventInit start
INFO: Adding LockCleaner
Feb 16, 2011 4:27:47 PM com.openexchange.mailaccount.internal.MailAccountStorageInit start
INFO: MailAccountStorageService successfully injected to server service registry
Feb 16, 2011 4:27:47 PM com.openexchange.server.impl.Starter adminStart
INFO: Admin successfully initialized.
Feb 16, 2011 4:27:47 PM com.openexchange.server.impl.Starter adminStart
INFO: SYSTEM IS UP & RUNNING IN ADMIN MODE...
Feb 16, 2011 4:27:47 PM com.openexchange.proxy.servlet.osgi.ServletRegisterer tryRegistering
SEVERE: Not initialized, yet.
Throwable occurred: javax.servlet.ServletException: Not initialized, yet.
        at com.openexchange.tools.servlet.http.manager.DummyHttpServletManager.registerServlet(DummyHttpServletManager.java:90)
        at com.openexchange.tools.servlet.http.HttpServletManager.registerServlet(HttpServletManager.java:108)
        at com.openexchange.tools.servlet.http.osgi.HttpServiceImpl.registerServlet(HttpServiceImpl.java:90)
        at com.openexchange.proxy.servlet.osgi.ServletRegisterer.tryRegistering(ServletRegisterer.java:47)
        at com.openexchange.proxy.servlet.osgi.ServletRegisterer.addingService(ServletRegisterer.java:38)
        at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1064)
        at org.osgi.util.tracker.ServiceTracker$Tracked.track(ServiceTracker.java:1042)
        at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:967)
        at org.eclipse.osgi.framework.internal.core.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:94)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:1224)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195)
        at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:141)
        at org.eclipse.osgi.framework.internal.core.Framework.publishServiceEventPrivileged(Framework.java:1603)
        at org.eclipse.osgi.framework.internal.core.Framework.publishServiceEvent(Framework.java:1578)
        at org.eclipse.osgi.framework.internal.core.ServiceRegistrationImpl.<init>(ServiceRegistrationImpl.java:103)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.createServiceRegistration(BundleContextImpl.java:657)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:609)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:675)
        at com.openexchange.server.osgi.ServerActivator.startBundle(ServerActivator.java:528)
        at com.openexchange.server.osgiservice.DeferredActivator.signalAvailability(DeferredActivator.java:278)
        at com.openexchange.server.osgiservice.DeferredActivator$DeferredSTC.addingService(DeferredActivator.java:102)
        at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1064)
        at org.osgi.util.tracker.ServiceTracker$Tracked.track(ServiceTracker.java:1042)
        at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:967)
        at org.eclipse.osgi.framework.internal.core.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:94)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:1224)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195)
        at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:141)
        at org.eclipse.osgi.framework.internal.core.Framework.publishServiceEventPrivileged(Framework.java:1603)
        at org.eclipse.osgi.framework.internal.core.Framework.publishServiceEvent(Framework.java:1578)
        at org.eclipse.osgi.framework.internal.core.ServiceRegistrationImpl.<init>(ServiceRegistrationImpl.java:103)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.createServiceRegistration(BundleContextImpl.java:657)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:609)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:675)
        at org.eclipse.equinox.event.Activator.start(Activator.java:26)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:999)
        at java.security.AccessController.doPrivileged(AccessController.java:251)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:993)
        at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:974)
        at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:350)
        at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1118)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:634)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282)
        at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468)
        at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195)
        at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:297)
Feb 16, 2011 4:27:47 PM com.openexchange.caching.internal.JCSCacheServiceInit loadConfiguration
INFO: JCS caching system successfully configured with properties from input stream.
Feb 16, 2011 4:27:48 PM com.openexchange.folderstorage.osgi.FolderStorageActivator start
INFO: Bundle "com.openexchange.folderstorage" successfully started!
Feb 16, 2011 4:28:06 PM org.apache.jcs.auxiliary.lateral.socket.tcp.LateralTCPService <init>
SEVERE: Could not create sender to [127.0.0.1:57462] -- Socket is null, cannot connect to 127.0.0.1:57462
Feb 16, 2011 4:28:06 PM org.apache.jcs.auxiliary.lateral.socket.tcp.LateralTCPCacheManager fixService
SEVERE: Can't fix Socket is null, cannot connect to 127.0.0.1:57462
Feb 16, 2011 4:28:06 PM org.apache.jcs.auxiliary.lateral.LateralCacheRestore canFix
SEVERE: Can't fix Can't fix Socket is null, cannot connect to 127.0.0.1:57462
Feb 16, 2011 4:28:06 PM org.apache.jcs.auxiliary.lateral.socket.tcp.LateralTCPService <init>
SEVERE: Could not create sender to [127.0.0.1:57462] -- Socket is null, cannot connect to 127.0.0.1:57462
Feb 16, 2011 4:28:06 PM org.apache.jcs.auxiliary.lateral.socket.tcp.LateralTCPCacheManager fixService
SEVERE: Can't fix Socket is null, cannot connect to 127.0.0.1:57462
Feb 16, 2011 4:28:06 PM org.apache.jcs.auxiliary.lateral.LateralCacheRestore canFix
SEVERE: Can't fix Can't fix Socket is null, cannot connect to 127.0.0.1:57462
Feb 16, 2011 4:28:06 PM org.apache.jcs.auxiliary.lateral.socket.tcp.LateralTCPService <init>
SEVERE: Could not create sender to [127.0.0.1:57462] -- Socket is null, cannot connect to 127.0.0.1:57462
Feb 16, 2011 4:28:06 PM org.apache.jcs.auxiliary.lateral.socket.tcp.LateralTCPCacheManager fixService
SEVERE: Can't fix Socket is null, cannot connect to 127.0.0.1:57462
Feb 16, 2011 4:28:06 PM org.apache.jcs.auxiliary.lateral.LateralCacheRestore canFix
SEVERE: Can't fix Can't fix Socket is null, cannot connect to 127.0.0.1:57462
Feb 16, 2011 4:28:06 PM org.apache.jcs.auxiliary.lateral.socket.tcp.LateralTCPService <init>
SEVERE: Could not create sender to [127.0.0.1:57462] -- Socket is null, cannot connect to 127.0.0.1:57462
Feb 16, 2011 4:28:06 PM org.apache.jcs.auxiliary.lateral.socket.tcp.LateralTCPCacheManager fixService
SEVERE: Can't fix Socket is null, cannot connect to 127.0.0.1:57462
Feb 16, 2011 4:28:06 PM org.apache.jcs.auxiliary.lateral.LateralCacheRestore canFix
SEVERE: Can't fix Can't fix Socket is null, cannot connect to 127.0.0.1:57462
          Die Frage ist wie ich schon eine bestehende Database in den neuen Konfiguration registrieren? Denn es kann eingetlich nur daran liegen. Nur wie bewerkstelligt man das? BITTE HILFE. Müssen auf SE wegen BMClient.

          Gruss
          Steini
          Tags: None
          Previous template Next
          Working...
          X