Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved File takes a long time to load

    Collabora Online (CODE)
    3
    8
    258
    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.
    • E
      ekevu123 last edited by

      I have a dedicated server running Cloudron and Nextcloud and Collabora as separate applications on the same server.

      When I am trying to open a long file with pictures, it takes endless time to open and I somehow suspect it's the editor's fault because of what I found in the logs during the file loading process:

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297249 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:3072:122880:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297361 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:12288:122880:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297370 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:0:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297376 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:3072:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297382 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:6144:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297388 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:9216:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297393 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:12288:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297399 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:0:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297404 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:3072:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297409 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:6144:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297414 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:9216:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297419 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:12288:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297425 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:0:132096:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297430 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:3072:132096:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297436 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:6144:132096:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297441 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:9216:132096:3072:3072:0 was dropped because of time out (5618ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297446 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:12288:132096:3072:3072:0 was dropped because of time out (5618ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

      However, I don't know what to do with that. Can someone help?

      girish 1 Reply Last reply Reply Quote 0
      • girish
        girish Staff @ekevu123 last edited by

        @ekevu123 Since collabora is stateless, maybe you can try re-setting up collabora? How big is this file and how many pictures?

        1 Reply Last reply Reply Quote 1
        • nebulon
          nebulon Staff last edited by

          Also do you see anything in the nextcloud, collabora app or browser logs? I think the logs you posted are from collabora and could also indicate a resource issue if those tiles couldn't be created in-time. Do you see high cpu or memory loads while having the issue?

          E 1 Reply Last reply Reply Quote 0
          • E
            ekevu123 @nebulon last edited by

            @nebulon I just looked at the top command inside the Collabora app in Cloudron and never got the processor over 10% usage when scrolling through the document in different browsers. Same goes for the Nextcloud app, but since this is a rendering issue in Collabora, I wouldn't expect Nextcloud to react strangely anyway.

            The file is 297KB with only a few small screenshots.

            I can try re-setting up Collabora, but I didn't change anything from the standard configuration anyway, except giving it more resources in the Cloudron admin dashboard.

            nebulon 1 Reply Last reply Reply Quote 0
            • nebulon
              nebulon Staff @ekevu123 last edited by

              @ekevu123 if this is only happening with selected documents then it may be worth reporting this (possibly including the document itself) upstream with collabora as then this is more likely a bug or regression in the app itself, rather than Cloudron.

              E 1 Reply Last reply Reply Quote 1
              • E
                ekevu123 @nebulon last edited by

                @nebulon It is happening also with similarly big files (as in many pages, not big file size). I don't think it's necessarily a Cloudron issue, but it would still be great to understand if there are ways how this could be resolved.

                nebulon 1 Reply Last reply Reply Quote 1
                • nebulon
                  nebulon Staff @ekevu123 last edited by

                  @ekevu123 most likely only upstream will be able to track such an issue down, so it may be worth raising the issue there as well. Further, do you have an example document which you could share to reproduce this?

                  E 1 Reply Last reply Reply Quote 1
                  • E
                    ekevu123 @nebulon last edited by

                    @nebulon I can't share the original document publicly, unfortunately, but the problem has disappeared after having raised the PHP Memory Limit in Nextcloud from 512 MB to 2 GB.

                    1 Reply Last reply Reply Quote 3
                    • Topic has been marked as a question  nebulon nebulon 
                    • Topic has been marked as solved  nebulon nebulon 
                    • First post
                      Last post
                    Powered by NodeBB