XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XS 7.0.0, xoa 5.74.3, no consoles

    Scheduled Pinned Locked Moved Xen Orchestra
    11 Posts 2 Posters 470 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      Hi,

      We need more information if you want so help 🙂

      1. Are you using XO from the sources or XOA? If from the sources, which commit exactly?
      2. Do you have any error log in the browser console our XO output log?
      Q 1 Reply Last reply Reply Quote 0
      • Q Offline
        qnetter @olivierlambert
        last edited by

        @olivierlambert 1) XOA

        1. No browser log because of the stripped production build, alas; where is the XO log?

        Can this possibly be a firewall issue, either on the XS server or the VMs? 80 and 443 are open but not much else.

        1 Reply Last reply Reply Quote 0
        • olivierlambertO Offline
          olivierlambert Vates 🪐 Co-Founder CEO
          last edited by

          80 and 443 should be enough, as long as you are in the same network (or reachable, not a NAT for example)

          Q 1 Reply Last reply Reply Quote 0
          • Q Offline
            qnetter @olivierlambert
            last edited by

            @olivierlambert Definitely reachable.

            XO logs?

            1 Reply Last reply Reply Quote 0
            • olivierlambertO Offline
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by olivierlambert

              Browser log or XO logs 🙂

              edit: alternatively, restart the toolstack on the hosts

              Q 1 Reply Last reply Reply Quote 0
              • Q Offline
                qnetter @olivierlambert
                last edited by

                @olivierlambert I have already restarted the tool stack.

                Safari told me it can't see logs from the production build - I will try Chrome.

                Where are the XO logs - that was my original question.

                1 Reply Last reply Reply Quote 0
                • olivierlambertO Offline
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by

                  If there's an error, you should see in the output of xo-server program. On XOA, it's written on the MOTD when you connect in SSH 🙂

                  Q 1 Reply Last reply Reply Quote 0
                  • Q Offline
                    qnetter @olivierlambert
                    last edited by olivierlambert

                    @olivierlambert I'm seeing in the browser:

                    objc[49945]: Class WebSwapCGLLayer is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/Frameworks/libANGLE-shared.dylib (0x7ffb53eb4ec8) and /Applications/Google Chrome.app/Contents/Frameworks/Google Chrome Framework.framework/Versions/107.0.5304.87/Libraries/libGLESv2.dylib (0x10f0e0ed8). One of the two will be used. Which one is undefined.
[49934:259:1031/131940.589622:ERROR:account_info_fetcher.cc(62)] OnGetTokenFailure: Invalid credentials (credentials rejected by server).
[49947:11779:1031/131958.215231:ERROR:ssl_client_socket_impl.cc(982)] handshake failed; returned -1, SSL error code 1, net_error -207
[49947:11779:1031/131958.215336:ERROR:ssl_client_socket_impl.cc(982)] handshake failed; returned -1, SSL error code 1, net_error -207

                    And on XOA:

                    Oct 31 12:20:48 xoa su[95003]: (to xoa-support) root on none
Oct 31 12:20:48 xoa su[95003]: pam_unix(su-l:session): session opened for user xoa-support(uid=1001) by (uid=0)
Oct 31 12:20:49 xoa su[95003]: pam_unix(su-l:session): session closed for user xoa-support
Oct 31 12:40:22 xoa su[96868]: (to xoa-support) root on none
Oct 31 12:40:22 xoa su[96868]: pam_unix(su-l:session): session opened for user xoa-support(uid=1001) by (uid=0)
Oct 31 12:40:23 xoa su[96868]: pam_unix(su-l:session): session closed for user xoa-support
Oct 31 16:16:54 xoa su[115150]: (to xoa-support) root on none
Oct 31 16:16:54 xoa su[115150]: pam_unix(su-l:session): session opened for user xoa-support(uid=1001) by (uid=0)
Oct 31 16:16:55 xoa su[115150]: pam_unix(su-l:session): session closed for user xoa-support
Oct 31 16:20:17 xoa su[115514]: (to xoa-support) root on none
Oct 31 16:20:17 xoa su[115514]: pam_unix(su-l:session): session opened for user xoa-support(uid=1001) by (uid=0)
Oct 31 16:20:17 xoa su[115514]: pam_unix(su-l:session): session closed for user xoa-support
Oct 31 16:20:40 xoa xo-server[511]: 2022-10-31T20:20:40.291Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:41 xoa xo-server[511]: 2022-10-31T20:20:41.424Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:42 xoa xo-server[511]: 2022-10-31T20:20:42.387Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:43 xoa xo-server[511]: 2022-10-31T20:20:43.536Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:44 xoa xo-server[511]: 2022-10-31T20:20:44.542Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:45 xoa xo-server[511]: 2022-10-31T20:20:45.667Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:47 xoa xo-server[511]: 2022-10-31T20:20:47.771Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:48 xoa xo-server[511]: 2022-10-31T20:20:48.890Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:51 xoa xo-server[511]: 2022-10-31T20:20:51.883Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:53 xoa xo-server[511]: 2022-10-31T20:20:53.011Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:58 xoa xo-server[511]: 2022-10-31T20:20:58.117Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:20:59 xoa xo-server[511]: 2022-10-31T20:20:59.246Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:21:07 xoa xo-server[511]: 2022-10-31T20:21:07.044Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:21:08 xoa xo-server[511]: 2022-10-31T20:21:08.171Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:21:20 xoa xo-server[511]: 2022-10-31T20:21:20.646Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:21:22 xoa xo-server[511]: 2022-10-31T20:21:22.096Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:21:43 xoa xo-server[511]: 2022-10-31T20:21:43.641Z xo:main INFO + Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
Oct 31 16:21:44 xoa xo-server[511]: 2022-10-31T20:21:44.764Z xo:main INFO - Console proxy (rogerk@queernet.org - ::ffff:75.172.1.252)
                    1 Reply Last reply Reply Quote 0
                    • olivierlambertO Offline
                      olivierlambert Vates 🪐 Co-Founder CEO
                      last edited by

                      Are you in HTTPS in your browser? Same result with Firefox?

                      Q 1 Reply Last reply Reply Quote 0
                      • Q Offline
                        qnetter @olivierlambert
                        last edited by

                        @olivierlambert I was not, and cert is invalid, but when I override I get the same result. I will fix the cert and try again.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post