problema de acceso

DD ES March 12, 2022

buenos dias, al poner la contraseña me aparece el siguiente mensaje

 

Se han producido los siguientes errores:

  • Ocurrió un error al intentar iniciar sesión. Vuelve a intentarlo y ponte en contacto con tu administrador si el problema continúa.

 

¿como lo puedo solucionar?

3 answers

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 12, 2022

You will need to talk to the administrators of your Confluence system - they probably need to read the log files to find out what has gone wrong.

Deberá hablar con los administradores de su sistema Confluence; probablemente necesiten leer los archivos de registro para averiguar qué salió mal.

DD ES March 13, 2022

muchas gracias, resulta que el administrador ha dejado de trabajar en la compañía y ahora soy yo el que se encarga de esto. desconozco el sistema por completo y necesito ayuda.

Que logs son los que tendría que leer para saber el problema?

 

muchas gracias

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 13, 2022

Ok, welcome to the world of Atlassian Administration!

The log to start with is in < confluence home >/logs and is called atlassian-confluence.log - that is the main application log which usually records most errors.  There may be other files in that directory with errors as well, for some problems.  If Confluence is not starting at all, you may want to look at < confluence installation > /logs/Catalina.out

 

Vale, ¡bienvenido al mundo de Atlassian Administration!

El registro para empezar está en <confluence home> y se llama atlassian-confluence.log, que es el registro principal de la aplicación que generalmente registra la mayoría de los errores. Puede haber otros archivos en ese directorio con errores también, por algunos problemas. Si Confluence no se inicia en absoluto, es posible que desee ver < confluence installation > /logs/Catalina.out

DD ES March 14, 2022

buenso dias y muchas gracias por la ayuda

he revisado el log y veo este error

ERROR Could not find value for key log4j.appender.luceneQuerylog4j:ERROR Could not instantiate appender named "luceneQuery".
log4j:ERROR Could not instantiate appender named "luceneQuery".
log4j:ERROR Could not find value for key log4j.appender.luceneQuery
log4j:ERROR Could not instantiate appender named "luceneQuery".
12-Mar-2022 13:23:24.627 INFO [Catalina-utility-2] org.apache.catalina.core.ApplicationContext.log Initializing Spring DispatcherServlet 'dispatcher'
13:23:24 [Catalina-utility-2] o.a.c.c.C.[.[.[/synchrony-proxy][INFO] log - Initializing Spring DispatcherServlet 'dispatcher'
2022-03-12 13:23:24,875 INFO [Catalina-utility-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 7.13.1 [build 8703 based on commit hash 667f8fbbb27ecb3ada2b3cf97802739510a2b3c7$
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.atlassian.hibernate.adapter.proxy.BytecodeProviderImpl_ImplementV2Proxy (file:/opt/atlassian/confluence/confluence/WEB-INF/lib/hibernate.adapter-1.0.3.jar) to field$
WARNING: Please consider reporting this to the maintainers of com.atlassian.hibernate.adapter.proxy.BytecodeProviderImpl_ImplementV2Proxy
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Security framework of XStream not explicitly initialized, using predefined black list on your own risk.
12-Mar-2022 13:24:06.312 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8090"]
12-Mar-2022 13:24:06.317 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["https-jsse-nio2-8443"]
12-Mar-2022 13:24:06.318 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [42613] milliseconds
13:24:06 [http-nio-8090-exec-1] o.e.j.u.log[INFO] initialized - Logging initialized @43688ms to org.eclipse.jetty.util.log.Slf4jLog
12-Mar-2022 13:24:11.584 INFO [https-jsse-nio2-8443-exec-3] com.sun.jersey.server.impl.application.WebApplicationImpl._initiate Initiating Jersey application, version 'Jersey: 1.19.4 05/24/2017 03:20 PM'
12-Mar-2022 13:24:12.668 INFO [https-jsse-nio2-8443-exec-23] com.sun.jersey.server.impl.application.WebApplicationImpl._initiate Initiating Jersey application, version 'Jersey: 1.19.4 05/24/2017 03:20 PM'
12-Mar-2022 13:25:43.779 INFO [https-jsse-nio2-8443-exec-1] com.sun.jersey.server.impl.application.WebApplicationImpl._initiate Initiating Jersey application, version 'Jersey: 1.19.4 05/24/2017 03:20 PM'
12-Mar-2022 21:50:30.304 INFO [https-jsse-nio2-8443-exec-11] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in the HTTP protocol [HTTP/1.10x0aHost:]
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:559)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:261)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:893)
at org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1685)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1167)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:613)
at org.apache.tomcat.util.net.Nio2Endpoint$Nio2SocketWrapper$2.completed(Nio2Endpoint.java:591)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:996)
at org.apache.tomcat.util.net.SecureNio2Channel$1.completed(SecureNio2Channel.java:925)
at java.base/sun.nio.ch.Invoker.invokeUnchecked(Unknown Source)
at java.base/sun.nio.ch.Invoker$2.run(Unknown Source)
at java.base/sun.nio.ch.AsynchronousChannelGroupImpl$1.run(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 14, 2022

This could be one of a number of things, and probably needs to be traced further through the rest of the logs.  Are there more lines of error?

Do you know what started causing this error?  Did you upgrade or (re)install the system?  

0 votes
Ashley Yepez April 17, 2024

error_wiki.png

Hola buenas tardes, yo también tengo un problema similar, nuestro admin. ha dejado la compañía y poco después a mi me aparece este mensaje, por lo que no sé a quien contactar para que me pueda ayudar con este problema por favor.

0 votes
DD ES March 17, 2022

Es probable que se hiciera una actualizacion, necesito ayuda para resolver el problema... reiniciando SQL se podria resolver??

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events