[Résolu] Problème d'auth Bluemind version 1.0.9422 / Debian-Squeeze

BlueMind - FR Discussions
1

Bonjour,

je viens de faire une mise à jour de mon système et curieusement je n’arrive plus à me connecter avec mes utilisateurs en imap ou web.

les messages sont les suivants :

==> bm-locator/locator.log <==
2013-09-28 13:22:59,646 n.b.l.i.LocatorDbHelper ERROR - net/bluemind/pool/BMPoolActivator
java.lang.NoClassDefFoundError: net/bluemind/pool/BMPoolActivator
at net.bluemind.locator.impl.LocatorDbHelper.findAssignedHosts(LocatorDbHelper.java:95) ~[net.bluemind.locator_1.0.0.b9422.jar:na]
at net.bluemind.locator.HostLocationServlet.doGet(HostLocationServlet.java:77) [net.bluemind.locator_1.0.0.b9422.jar:na]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) [javax.servlet_2.5.0.v201103041518.jar:na]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) [javax.servlet_2.5.0.v201103041518.jar:na]
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) [org.eclipse.equinox.http.registry_1.1.100.v20110502.jar:na]
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) [org.eclipse.equinox.http.servlet_1.1.200.v20110502.jar:na]
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126) [org.eclipse.equinox.http.servlet_1.1.200.v20110502.jar:na]
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68) [org.eclipse.equinox.http.servlet_1.1.200.v20110502.jar:na]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) [javax.servlet_2.5.0.v201103041518.jar:na]
at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:317) [org.eclipse.equinox.http.jetty_2.0.100.v20110502.jar:na]
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) [org.mortbay.jetty.server_6.1.23.v201012071420.jar:na]
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) [org.mortbay.jetty.server_6.1.23.v201012071420.jar:na]
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) [org.mortbay.jetty.server_6.1.23.v201012071420.jar:na]
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) [org.mortbay.jetty.server_6.1.23.v201012071420.jar:na]
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) [org.mortbay.jetty.server_6.1.23.v201012071420.jar:na]
at org.mortbay.jetty.Server.handle(Server.java:326) [org.mortbay.jetty.server_6.1.23.v201012071420.jar:na]
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) [org.mortbay.jetty.server_6.1.23.v201012071420.jar:na]
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:924) [org.mortbay.jetty.server_6.1.23.v201012071420.jar:na]
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) [org.mortbay.jetty.server_6.1.23.v201012071420.jar:na]
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) [org.mortbay.jetty.server_6.1.23.v201012071420.jar:na]
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) [org.mortbay.jetty.server_6.1.23.v201012071420.jar:na]
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228) [org.mortbay.jetty.server_6.1.23.v201012071420.jar:na]
at org.mortbay.jetty.security.SslSocketConnector$SslConnection.run(SslSocketConnector.java:680) [org.mortbay.jetty.server_6.1.23.v201012071420.jar:na]
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) [org.mortbay.jetty.util_6.1.23.v201012071420.jar:na]
2013-09-28 13:22:59,646 n.b.l.HostLocationServlet ERROR - Could not find bm/core for admin0@global.virt

==> bm-hps/hps.log <==
2013-09-28 13:22:59,647 n.b.p.h.i.HttpProxyServerHandler INFO - Missing or invalid BMHPS cookie, /bluemind_sso_security need reauth
2013-09-28 13:22:59,648 n.b.p.h.i.HttpProxyServerHandler INFO - reusing stored request id X

J’avoue que je ne sais pas trop vers où regarder :confused:

Sacha.

2

/var/log/postgresql/postgresql-8.4-main.log
2013-09-28 15:35:45 CEST FATAL: could not create shared memory segment: Invalid argument
2013-09-28 15:35:45 CEST DETAIL: Failed system call was shmget(key=5432001, size=226353152, 03600).
2013-09-28 15:35:45 CEST HINT: This error usually means that PostgreSQL’s request for a shared memory segment exceeded your kernel’s SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 226353152 bytes), reduce PostgreSQL’s shared_buffers parameter (currently 25600) and/or its max_connections parameter (currently 103).
If the request size is already small, it’s possible that it is less than your kernel’s SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.
The PostgreSQL documentation contains more information about shared memory configuration.
2013-09-28 17:49:39 CEST FATAL: could not create shared memory segment: Invalid argument
2013-09-28 17:49:39 CEST DETAIL: Failed system call was shmget(key=5432001, size=226353152, 03600).
2013-09-28 17:49:39 CEST HINT: This error usually means that PostgreSQL’s request for a shared memory segment exceeded your kernel’s SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 226353152 bytes), reduce PostgreSQL’s shared_buffers parameter (currently 25600) and/or its max_connections parameter (currently 103).
If the request size is already small, it’s possible that it is less than your kernel’s SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.
The PostgreSQL documentation contains more information about shared memory configuration.

3

corrigé avec kernel.shmmax=300000000 :rolleyes: