Channel manager works but disable after a variable time


#1

We have a production environment with a Ibm http, proxing site deployed inside a websphere 8.5 and it works great.

In the websphere we have a ear, with site.war in a root context path, and cms.war in /cms.

We configure al things in ibm http and hippo console to show the site, under root context path, and works.

And channel manager works, accesing in the intranet directly to the websphere, but… after a time, variable, we see the: “This perspective could not be loaded…”
We have a production environment with a Ibm http, proxing site deployed inside a websphere 8.5 and it works great.

In the websphere we have a ear, with site.war in a root context path, and cms.war in /cms.

We configure al things in ibm http, websphere and hippo console to show the site, under root context path, and works.

And channel manager works, accesing in the intranet directly to the websphere, but… after a time, variable, we see the: “This perspective could not be loaded…”

In which circumstances, RestProxyServicesManager disable the channel manager? only at startup? maybe something in or “firewall” do something and the internal loop call are closed?

Please any clue will be well come :slight_smile:


#2

Hi,

please see


#3

Hi @jasper.floor notice that “it works arround an hour” and later… i start to see “This perspective could not be loaded…” my underlaying question was… “In which circumstances, RestProxyServicesManager disable the channel manager” hope you can point me to the right direction to discover what in my enviroment cause after a while from a server restart that “close of channel manager”.


#4

hi @niklas.winkels a point to documents that explain: when the channel editor is disabled, until the next restart?

Thanks.


#5

Hi,

I’ve been out, it sounds like you still have this problem? I wouldn’t expect the CM to stop working after an hour, it should either not work at all or just work. It may have something to with websphere, but I have no experience with that and we do not test against it (it is not part of our supported stack). Since it did work initially, check where the requests are going and what the response is.


#6

Yes i still have the problem :cry: i would like to know the responsible of display the message: “This perspective could not be loaded. This is caused by the CMS not being able to connect to the site, either because the site is down or due to a misconfiguration. Please contact your system administrator.” because when i restart the websphere it works, but later it’s appear, we started playing with “/hippo:configuration/hippo:frontend/cms/cms-services/hstRestProxyService” because we move site.war to context root inside ear… but… “something” disable channel manager under certains circumstances… if we would knew “who” may we discover our problem over “not supported platform :)”


#7

The CM is only disabled because it can’t reach that endpoint. So it is the front end giving up. Check the request and especially the path the request takes. EG, configuration on a proxy somewhere may not be correct.


#8

If i understand you well, when the “inner call” fail.

@jeroen.hoffman talks in this old post https://groups.google.com/forum/#!msg/hippo-community/5prZRRNhJ4Y/JtiGSu7WjDsJ “This call will always be an internal call. It should not end up in your apache logs, since it should go directly to you app container (tomcat).The host is always bound to 127.0.0.1 and the port you run your app container on.”

This part confuse me, maybe the front “make a last call to disable”?

As you can see, we configure the entry app to have a root context…

1º Maybe i miss some other place where “remove” site.
2º Can you talk about the “internal call”, its over AJP?

Thanks a lot for your help.


#9

If the CM is working and then stops it doesn’t sound like a problem with configuration of the cms. Maybe it’s something in websphere?


#10

maybe… because of this, i’m trying to discover the part of the code that “disable” to figure how to solve it :frowning:


#11

The frontend is trying to reach the backend. It can’t reach it so it shows that. It isn’t being disabled by the code. This would be happening in the JS client side. Why it can’t reach the server is unclear. Can you reach the cms locally? ie, with a browser on the node running the cms?


#12

Perfect… in this case, we discard this option and center in the “conectivity” issues… the case was, when we restart the webshere, it’s works again, this confuse us…

1º We will review conectivity and all the “_rp/cafebabe-cafe-babe-cafe-babecafebabe./keepalive”, another url from the frontend to track?

2º Remember, we change the root context, and it’s works. Another place where change to “discard” /site?

Thanks a lot for your help.


#13

It’s not that the frontend, i.e. your browser, cannot reach the backend. It’s the CMS webapp that cannot reach the site webapp. The CMS does server-side REST calls to the site webapp. Or more specifically: to the URL configured in the property /hippo:configuration/hippo:frontend/cms/cms-services/hstRestProxyService/rest.uri . By default that property is set to “http://127.0.0.1/site/_cmsrest”. To check whether the site webapp is still up the CMS periodically does a GET call. With the default configuration that call goes to http://127.0.0.1/site/_cmsrest/sites/_isAlive. When that call times out the CMS considers the site to be down, and shows the “perspective could not be loaded” message instead of the Channel Manager UI.

These server-side REST calls cannot be observed in the browser. They happen server-side, from one webapp to the other. As explained in [1], they can be observed by enabling HST diagnostics in the site webapp.

As for why the calls work initially but fail later on: that’s most likely a server-side configuration problem related to Websphere. Are calls to 127.0.0.1 treated specially somehow?

Mathijs

[1] https://www.onehippo.org/library/concepts/channels/channel-manager-troubleshooting.html#perspective_could_not_be_loaded


#14

hi @mathijs thanks for the detailed explanation i have more “concrete” question about to discover my problem :slight_smile:

1º You said

To check whether the site webapp is still up the CMS periodically does a GET call. With the default configuration that call goes to http://127.0.0.1/site/_cmsrest/sites/_isAlive.

this url is build with rest.uri+ping.service.uri or directly with ping.service.uri

2º As you said, we active the log and see this call working. We are going to reboot the server, and observe this logs, and try manualy curl call inside the server … maybe some firewall close the conection, or some temporally timeout because the “latency”… the question, is there some property inside /cms/console to activate de CM again without reboot the entry server?

We’ll try this days diagnostic the problem, focusing on the net and the ping url.

Thanks a lot. Stay tunned :wink:


#15

The ‘ping’ URL is build using the rest.uri property only. The ping.service.uri property is a legacy left-over and not used anymore. I’ve created [1] to remove it. The /sites/_isAlive part is hardcoded in the SiteService interface [2], which the CMS uses to talk REST to the site webapp (via a proxy created by Apache CXF).

The server-side-ping-logic can be found in the RestProxyServicesManager class [3]. There’s an active job in there that repeatedly checks whether all site webapps(s) are up, via a GET to <rest.uri>/sites/_isAlive. When the GET fails (or the endpoint returns false, which should not happen since the implementation is simply “return true”) the site is marked as ‘down’ and re-checked one minute later.

One thing to note when testing all this is that the redraw behavior of the Channels section in the CMS is a little inconsistent. Consider these two use cases:

a. site is up > user logs and clicks Channels (channels are shown) > site goes down

The ‘frontend pinger’ of the CMS (i.e. the browser pinging the backed) will redraw the Channels section, by default after 20 seconds. All channels will then vanish, but the ‘Add Channel’ top bar etc. remains visible. When the site comes back up, the channels will re-appear automatically again after 20 seconds.

b. site is down > user logs and clicks Channels (message is shown) > site comes up

In this case the ‘pinger’ of the CMS will not redraw the Channels. The message remains visible, even after the site has come up. The only way to see the channels again in the CMS is to log out and in again.

You can play these scenario’s locally using “mvn cargo:undeploy” and “mvn cargo:deploy” in the ‘site’ folder to undeploy and redeploy the site webapp while the CMS webapp keeps running [4].

hope that helps,
Mathijs

[1] https://issues.onehippo.com/browse/CHANNELMGR-2126

[2] https://code.onehippo.org/cms-community/hippo-site-toolkit/blob/hst-5.4.0/cms-restapi/src/main/java/org/hippoecm/hst/rest/SiteService.java#L31

[3] https://code.onehippo.org/cms-community/hippo-addon-channel-manager/blob/hippo-addon-channel-manager-5.3.0/frontend/src/main/java/org/onehippo/cms7/channelmanager/restproxy/RestProxyServicesManager.java#L70

[4] https://www.onehippo.org/library/development/run-and-develop-with-cargo.html


#16

@mathijs thanks a lot for this detailed explanation… i think this could be useful “for the comunity” :slight_smile:

I think we are “near” of the “root of my problem” in the begining i said:

In the websphere we have a ear, with site.war in a root context path, and cms.war in /cms.

and as you can see in the screencapture of my console we leave it “empty” the variable context.path because, maybe in an incorrect way, we remove “/site” from our website in this way (sure will be better do in apache proxy, but it’s another history). And because of this to enable channel manager (that works in the PRE enviroment) we leave empty.

Do you think because of this:

The question, if we remove /site changing the properties of console… maybe this version of channel manager don’t ping correctly?


#17

we leave it “empty” the variable context.path because, maybe in an incorrect way, we remove “/site” from our website in this way (sure will be better do in apache proxy, but it’s another history).

Leaving the context.path property empty is the correct way to do it, according to https://www.onehippo.org/library/deployment/configuring/deploy-application-as-root_war.html

BTW: what’s the Hippo CMS version you’re using?

Mathijs


#18

hi @mathijs i’m not sure… but it’s a 11.x.y …

i was working in my laptop (inside a virtualbox) with a fresh instalation following https://www.onehippo.org/11/trails/getting-started/hippo-essentials-getting-started.html and something strange happend me…

If i work inside the VirtualMaching all it’s ok (using firefox inside the debian install), but if i enter through host maching i saw this message in the console

[INFO] [talledLocalContainer] 11.10.2018 12:57:56 WARN  http-nio-8080-exec-6 [CmsRestSecurityValve.invoke:131] NullPointerException while processing CMS REST credentials : java.lang.NullPointerException
[INFO] [talledLocalContainer] 11.10.2018 12:57:56 WARN  Thread-43 [RestProxyServicesManager$2.run:150] Site for contextPath /site is not live. Re-checking in 60379 milliseconds. Cause: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error

and yesterday i saw something like this…

[INFO] [talledLocalContainer] 10.10.2018 17:33:00 WARN http-nio-8080-exec-3 [HstDelegateeFilterBean.doFilter:208] 'Request{ method='GET', scheme='http', host='10.145.6.127:8080', requestURI='/site/_rp/cafebabe-cafe-babe-cafe-babecafebabe./keepalive', queryString='null'}' can not be matched to a host. Skip HST Filter and request processing.

Inside…

Outside…

And a lot of errors :thinking::thinking:

[INFO] [talledLocalContainer] 11.10.2018 12:57:56 WARN  http-nio-8080-exec-6 [CmsRestSecurityValve.invoke:131] NullPointerException while processing CMS REST credentials : java.lang.NullPointerException
[INFO] [talledLocalContainer] 11.10.2018 12:57:56 WARN  Thread-43 [RestProxyServicesManager$2.run:150] Site for contextPath /site is not live. Re-checking in 60379 milliseconds. Cause: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error
[INFO] [talledLocalContainer] 11.10.2018 13:01:58 WARN  http-nio-8080-exec-6 [CmsRestSecurityValve.invoke:131] NullPointerException while processing CMS REST credentials : java.lang.NullPointerException
[INFO] [talledLocalContainer] 11.10.2018 13:01:58 WARN  http-nio-8080-exec-8 [BlueprintStore.getBlueprints:138] Failed to load blueprint for one or more rest proxies : java.util.concurrent.ExecutionException: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error
[INFO] [talledLocalContainer] 11.10.2018 13:01:58 WARN  http-nio-8080-exec-7 [CmsRestSecurityValve.invoke:131] NullPointerException while processing CMS REST credentials : java.lang.NullPointerException
[INFO] [talledLocalContainer] 11.10.2018 13:01:58 WARN  http-nio-8080-exec-8 [ChannelStore.canModifyChannels:420] Rest proxies did not return valid response whether user can modify channels. Return false as default
[INFO] [talledLocalContainer] 11.10.2018 13:01:58 WARN  http-nio-8080-exec-4 [CmsRestSecurityValve.invoke:131] NullPointerException while processing CMS REST credentials : java.lang.NullPointerException
[INFO] [talledLocalContainer] 11.10.2018 13:01:58 WARN  http-nio-8080-exec-8 [ChannelStore.canModifyChannels:420] Rest proxies did not return valid response whether user can modify channels. Return false as default
[INFO] [talledLocalContainer] 11.10.2018 13:02:03 WARN  http-nio-8080-exec-10 [CmsRestSecurityValve.invoke:131] NullPointerException while processing CMS REST credentials : java.lang.NullPointerException
[INFO] [talledLocalContainer] 11.10.2018 13:02:03 WARN  http-nio-8080-exec-2 [ChannelStore.loadChannels:508] Failed to load the channels for one or more rest proxies: java.util.concurrent.ExecutionException: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error
[INFO] [talledLocalContainer] 11.10.2018 13:02:03 WARN  http-nio-8080-exec-5 [CmsRestSecurityValve.invoke:131] NullPointerException while processing CMS REST credentials : java.lang.NullPointerException
[INFO] [talledLocalContainer] 11.10.2018 13:02:03 WARN  http-nio-8080-exec-2 [ChannelStore.loadChannels:508] Failed to load the channels for one or more rest proxies: java.util.concurrent.ExecutionException: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error
[INFO] [talledLocalContainer] 11.10.2018 13:02:03 WARN  http-nio-8080-exec-6 [HstDelegateeFilterBean.doFilter:208] 'Request{ method='GET', scheme='http', host='10.145.6.127:8080', requestURI='/site/_rp/cafebabe-cafe-babe-cafe-babecafebabe./keepalive', queryString='null'}' can not be matched to a host. Skip HST Filter and request processing. 
[INFO] [talledLocalContainer] 11.10.2018 13:02:04 WARN  http-nio-8080-exec-7 [CmsRestSecurityValve.invoke:131] NullPointerException while processing CMS REST credentials : java.lang.NullPointerException
[INFO] [talledLocalContainer] 11.10.2018 13:02:04 WARN  http-nio-8080-exec-1 [ChannelStore.loadChannels:508] Failed to load the channels for one or more rest proxies: java.util.concurrent.ExecutionException: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error
[INFO] [talledLocalContainer] 11.10.2018 13:02:05 WARN  http-nio-8080-exec-6 [CmsRestSecurityValve.invoke:131] NullPointerException while processing CMS REST credentials : java.lang.NullPointerException
[INFO] [talledLocalContainer] 11.10.2018 13:02:05 WARN  http-nio-8080-exec-2 [ChannelStore.loadChannels:508] Failed to load the channels for one or more rest proxies: java.util.concurrent.ExecutionException: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error
[INFO] [talledLocalContainer] 11.10.2018 13:02:24 WARN  http-nio-8080-exec-1 [HstDelegateeFilterBean.doFilter:208] 'Request{ method='GET', scheme='http', host='10.145.6.127:8080', requestURI='/site/_rp/cafebabe-cafe-babe-cafe-babecafebabe./keepalive', queryString='null'}' can not be matched to a host. Skip HST Filter and request processing. 
[INFO] [talledLocalContainer] 11.10.2018 13:02:24 WARN  http-nio-8080-exec-9 [CmsRestSecurityValve.invoke:131] NullPointerException while processing CMS REST credentials : java.lang.NullPointerException
[INFO] [talledLocalContainer] 11.10.2018 13:02:24 WARN  http-nio-8080-exec-7 [ChannelStore.loadChannels:508] Failed to load the channels for one or more rest proxies: java.util.concurrent.ExecutionException: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error
[INFO] [talledLocalContainer] 11.10.2018 13:02:44 WARN  http-nio-8080-exec-3 [HstDelegateeFilterBean.doFilter:208] 'Request{ method='GET', scheme='http', host='10.145.6.127:8080', requestURI='/site/_rp/cafebabe-cafe-babe-cafe-babecafebabe./keepalive', queryString='null'}' can not be matched to a host. Skip HST Filter and request processing. 
[INFO] [talledLocalContainer] 11.10.2018 13:02:46 WARN  http-nio-8080-exec-10 [CmsRestSecurityValve.invoke:131] NullPointerException while processing CMS REST credentials : java.lang.NullPointerException
[INFO] [talledLocalContainer] 11.10.2018 13:02:46 WARN  http-nio-8080-exec-5 [ChannelStore.loadChannels:508] Failed to load the channels for one or more rest proxies: java.util.concurrent.ExecutionException: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error
[INFO] [talledLocalContainer] 11.10.2018 13:03:05 WARN  http-nio-8080-exec-6 [HstDelegateeFilterBean.doFilter:208] 'Request{ method='GET', scheme='http', host='10.145.6.127:8080', requestURI='/site/_rp/cafebabe-cafe-babe-cafe-babecafebabe./keepalive', queryString='null'}' can not be matched to a host. Skip HST Filter and request processing. 
[INFO] [talledLocalContainer] 11.10.2018 13:03:06 WARN  http-nio-8080-exec-8 [CmsRestSecurityValve.invoke:131] NullPointerException while processing CMS REST credentials : java.lang.NullPointerException
[INFO] [talledLocalContainer] 11.10.2018 13:03:06 WARN  http-nio-8080-exec-2 [ChannelStore.loadChannels:508] Failed to load the channels for one or more rest proxies: java.util.concurrent.ExecutionException: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error

But if i enter the first time from the host machine…

main:
     [echo] Press Ctrl-C to stop the Cargo container...
[INFO] [talledLocalContainer] 11.10.2018 13:07:44 ERROR http-nio-8080-exec-6 [DefaultExceptionMapper.mapExpectedExceptions:144] Connection lost, give up responding.
[INFO] [talledLocalContainer] org.apache.wicket.protocol.http.servlet.ResponseIOException: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Tubería rota
[INFO] [talledLocalContainer] 	at org.apache.wicket.protocol.http.servlet.ServletWebResponse.write(ServletWebResponse.java:126)
[INFO] [talledLocalContainer] 	at org.apache.wicket.protocol.http.HeaderBufferingWebResponse.write(HeaderBufferingWebResponse.java:182)
[INFO] [talledLocalContainer] 	at org.apache.wicket.request.resource.PackageResource$1.writeData(PackageResource.java:328)
[INFO] [talledLocalContainer] 	at org.apache.wicket.request.resource.AbstractResource.respond(AbstractResource.java:528)
[INFO] [talledLocalContainer] 	at org.apache.wicket.request.handler.resource.ResourceRequestHandler.respond(ResourceRequestHandler.java:75)
[INFO] [talledLocalContainer] 	at org.apache.wicket.request.handler.resource.ResourceReferenceRequestHandler.respond(ResourceReferenceRequestHandler.java:108)
[INFO] [talledLocalContainer] 	at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:890)
[INFO] [talledLocalContainer] 	at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
[INFO] [talledLocalContainer] 	at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:261)
[INFO] [talledLocalContainer] 	at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:218)
[INFO] [talledLocalContainer] 	at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:289)
[INFO] [talledLocalContainer] 	at org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:259)
[INFO] [talledLocalContainer] 	at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:201)
[INFO] [talledLocalContainer] 	at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:282)
[INFO] [talledLocalContainer] 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
[INFO] [talledLocalContainer] 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
[INFO] [talledLocalContainer] 	at org.hippoecm.frontend.plugins.login.ConcurrentLoginFilter.doFilter(ConcurrentLoginFilter.java:54)
[INFO] [talledLocalContainer] 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
[INFO] [talledLocalContainer] 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
[INFO] [talledLocalContainer] 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212)
[INFO] [talledLocalContainer] 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
[INFO] [talledLocalContainer] 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
[INFO] [talledLocalContainer] 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)
[INFO] [talledLocalContainer] 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
[INFO] [talledLocalContainer] 	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)
[INFO] [talledLocalContainer] 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
[INFO] [talledLocalContainer] 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:528)
[INFO] [talledLocalContainer] 	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1100)
[INFO] [talledLocalContainer] 	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:687)
[INFO] [talledLocalContainer] 	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1520)
[INFO] [talledLocalContainer] 	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1476)
[INFO] [talledLocalContainer] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[INFO] [talledLocalContainer] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[INFO] [talledLocalContainer] 	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
[INFO] [talledLocalContainer] 	at java.lang.Thread.run(Thread.java:748)
[INFO] [talledLocalContainer] Caused by: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Tubería rota
[INFO] [talledLocalContainer] 	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:396)
[INFO] [talledLocalContainer] 	at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:426)
[INFO] [talledLocalContainer] 	at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:339)
[INFO] [talledLocalContainer] 	at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:421)
[INFO] [talledLocalContainer] 	at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:409)
[INFO] [talledLocalContainer] 	at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:97)
[INFO] [talledLocalContainer] 	at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:90)
[INFO] [talledLocalContainer] 	at org.apache.wicket.protocol.http.servlet.ServletWebResponse.write(ServletWebResponse.java:122)
[INFO] [talledLocalContainer] 	... 34 more
[INFO] [talledLocalContainer] Caused by: java.io.IOException: Tubería rota
[INFO] [talledLocalContainer] 	at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
[INFO] [talledLocalContainer] 	at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
[INFO] [talledLocalContainer] 	at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
[INFO] [talledLocalContainer] 	at sun.nio.ch.IOUtil.write(IOUtil.java:65)
[INFO] [talledLocalContainer] 	at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471)
[INFO] [talledLocalContainer] 	at org.apache.tomcat.util.net.NioChannel.write(NioChannel.java:124)
[INFO] [talledLocalContainer] 	at org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSelector.java:101)
[INFO] [talledLocalContainer] 	at org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.java:172)
[INFO] [talledLocalContainer] 	at org.apache.coyote.http11.InternalNioOutputBuffer.writeToSocket(InternalNioOutputBuffer.java:139)
[INFO] [talledLocalContainer] 	at org.apache.coyote.http11.InternalNioOutputBuffer.addToBB(InternalNioOutputBuffer.java:197)
[INFO] [talledLocalContainer] 	at org.apache.coyote.http11.InternalNioOutputBuffer.access$000(InternalNioOutputBuffer.java:41)
[INFO] [talledLocalContainer] 	at org.apache.coyote.http11.InternalNioOutputBuffer$SocketOutputBuffer.doWrite(InternalNioOutputBuffer.java:320)
[INFO] [talledLocalContainer] 	at org.apache.coyote.http11.filters.IdentityOutputFilter.doWrite(IdentityOutputFilter.java:84)
[INFO] [talledLocalContainer] 	at org.apache.coyote.http11.AbstractOutputBuffer.doWrite(AbstractOutputBuffer.java:256)
[INFO] [talledLocalContainer] 	at org.apache.coyote.Response.doWrite(Response.java:491)
[INFO] [talledLocalContainer] 	at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:391)
[INFO] [talledLocalContainer] 	... 41 more
[INFO] [talledLocalContainer] 11.10.2018 13:07:50 WARN  http-nio-8080-exec-9 [CmsRestSecurityValve.invoke:131] NullPointerException while processing CMS REST credentials : java.lang.NullPointerException
[INFO] [talledLocalContainer] 11.10.2018 13:07:51 WARN  Thread-41 [RestProxyServicesManager$2.run:150] Site for contextPath /site is not live. Re-checking in 64286 milliseconds. Cause: javax.ws.rs.InternalServerErrorException: HTTP 500 Internal Server Error

But from the host, works! without restart…

:thinking: I’m lost!


#19

@mathijs could you take a look at this situation? maybe because some internal feature, the exposition of /cms must be mandatory throuhg a reverse proxy?

Reviewing the documentation https://www.onehippo.org/library/deployment/configuring/configure-apache-httpd-as-reverse-proxy-for-hippo.html about this, this point me this https://www.onehippo.org/library/enterprise/installation-and-configuration/configure-virtual-hosts-in-an-environment.html

And there talk about

hst:cmslocation: https://cms.example.com

and before

ProxyPreserveHost On

And viewing the access over de VirtualMachine… maybe if cmslocation don’t match with the request ip this lead to a “disable error”?


#20

Hi @mathijs and @wouter.pasman i tried a lot of things… i come back to my original question: when the hippo server disable console? in a fresh start it works… but later it doesn’t… i think some kind of firewall or high load trigger that some timeout? disable the console…

which circumstances disable when at the beggining it’s open?

With this info, we maybe discover our problem… firewall maybe?

Thanks a lot.