z-mio opened a new issue, #9039:
URL: https://github.com/apache/cloudstack/issues/9039

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
    * Bug Report
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   noVNC
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   `cloudstack-agent 4.19.0.1`
   `cloudstack-management 4.19.0.1`
   `cloudstack-usage 4.19.0.1`
   `cloudstack-common 4.19.0.1`
   `CPVM systemvmtemplate-4.19.0-kvm`
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   
   N/A
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   
   `Ubuntu 22.04.4 LTS` 
   
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   I encountered the same issue as #8303. I manually replaced `${VNCPORT}` with 
8443 in `/etc/iptables/rules.v4`, and then re-executed 
`/opt/cloud/bin/setup/postinit.sh`
   
   After the modification, the VNC console page can be opened, but it is always 
connected
   
   I watched a lot of tutorials, but nothing worked
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal 
test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   sed -i 's/${VNCPORT}/8443/g' /etc/iptables/rules.v4
   sh /opt/cloud/bin/setup/postinit.sh
   tail -f /var/log/cloud/cloud.out
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   noVNC can be loaded normally
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   
   The noVNC console kept connecting until it timed out
   
   ![](https://img.155155155.xyz/i/2024/05/66376bd08bfd9.webp)
   
   This is the log
   
   <details>
   <summary>/var/log/cloud/cloud.out</summary>
   
   ~~~
   2024-05-05 10:05:54,362 INFO  
[cloud.consoleproxy.ConsoleProxyResourceHandler] (Thread-70:null) Get resource 
request for /resource/noVNC/vnc.html
   2024-05-05 10:05:54,367 INFO  
[cloud.consoleproxy.ConsoleProxyResourceHandler] (Thread-70:null) Sent file 
/resource/noVNC/vnc.html with content type text/html
   2024-05-05 10:05:56,402 INFO  [cloud.consoleproxy.ConsoleProxyNoVNCHandler] 
(qtp18310625-36:null) Get websocket connection request from remote IP : 
103.77.211.193
   2024-05-05 10:05:56,481 INFO  [cloud.consoleproxy.ConsoleProxyNoVncClient] 
(Thread-72:null) Connect to VNC server directly. host: 38.xx.221.14, port: 5901
   2024-05-05 10:05:56,505 INFO  [consoleproxy.vnc.NoVncClient] 
(Thread-72:null) Connecting to VNC server 38.xx.221.14:5901 ...
   2024-05-05 10:09:01,071 INFO  [cloud.consoleproxy.ConsoleProxyGCThread] 
(Console Proxy GC Thread:null) Dropping 
com.cloud.consoleproxy.ConsoleProxyNoVncClient@4b621b07 which has not been used 
for 184 seconds
   2024-05-05 10:10:56,482 ERROR [cloud.consoleproxy.ConsoleProxyNoVNCHandler] 
(Connector-Scheduler-371c7f21-1:null) Error on websocket
   org.eclipse.jetty.websocket.api.CloseException: 
java.util.concurrent.TimeoutException: Idle timeout expired: 300001/300000 ms
           at 
org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onReadTimeout(AbstractWebSocketConnection.java:564)
           at 
org.eclipse.jetty.io.AbstractConnection.onFillInterestedFailed(AbstractConnection.java:172)
           at 
org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillInterestedFailed(AbstractWebSocketConnection.java:539)
           at 
org.eclipse.jetty.io.AbstractConnection$ReadCallback.failed(AbstractConnection.java:317)
           at org.eclipse.jetty.io.FillInterest.onFail(FillInterest.java:140)
           at 
org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillableFail(SslConnection.java:591)
           at 
org.eclipse.jetty.io.ssl.SslConnection.onFillInterestedFailed(SslConnection.java:419)
           at 
org.eclipse.jetty.io.ssl.SslConnection$2.failed(SslConnection.java:170)
           at org.eclipse.jetty.io.FillInterest.onFail(FillInterest.java:140)
           at 
org.eclipse.jetty.io.AbstractEndPoint.onIdleExpired(AbstractEndPoint.java:407)
           at 
org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:171)
           at org.eclipse.jetty.io.IdleTimeout.idleCheck(IdleTimeout.java:113)
           at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
           at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
           at 
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
           at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
           at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
           at java.base/java.lang.Thread.run(Thread.java:829)
   Caused by: java.util.concurrent.TimeoutException: Idle timeout expired: 
300001/300000 ms
           ... 8 more
   ~~~
   
   </details>
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to