ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    ScreenConnect on CentOS is sluggish

    IT Discussion
    screenconnect centos 7
    5
    36
    4.8k
    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.
    • JaredBuschJ
      JaredBusch
      last edited by

      Session.db changed dramatically.

      [root@bnasc ~]# ls -l /opt/screenconnect/App_Data/Session.*
      -rw-r--r--. 1 root root    794624 Feb  6 11:41 /opt/screenconnect/App_Data/Session.db
      -rw-r--r--. 1 root root 322928640 Feb  6 11:29 /opt/screenconnect/App_Data/Session.db.2017.02.06
      -rw-r--r--. 1 root root     32768 Feb  6 11:50 /opt/screenconnect/App_Data/Session.db-shm
      -rw-r--r--. 1 root root   4128272 Feb  6 11:50 /opt/screenconnect/App_Data/Session.db-wal
      
      gjacobseG 1 Reply Last reply Reply Quote 1
      • gjacobseG
        gjacobse @JaredBusch
        last edited by

        @JaredBusch

        Question on that - Do you have the system do DB maintenance?0_1486403889779_2017-02-06 12_57_57-NTG Remote Portal.png

        JaredBuschJ 1 Reply Last reply Reply Quote 0
        • JaredBuschJ
          JaredBusch @gjacobse
          last edited by JaredBusch

          @gjacobse said in ScreenConnect on CentOS is sluggish:

          @JaredBusch

          Question on that - Do you have the system do DB maintenance?!

          That answer, is no. My bad on that.

          gjacobseG 1 Reply Last reply Reply Quote 0
          • gjacobseG
            gjacobse @JaredBusch
            last edited by

            @JaredBusch said in ScreenConnect on CentOS is sluggish:

            @gjacobse said in ScreenConnect on CentOS is sluggish:

            @JaredBusch

            Question on that - Do you have the system do DB maintenance?!

            That answer, is no. My bad on that.

            It wasn't set on the NTG system at first either. But once set, and allowed to cycle it's kept the DB in check. If you set today, it's likely that it won't process until the next run time, which will be Tuesday Night / Wednesday Morning....

            At least that is what SC Support explained to me.

            JaredBuschJ 1 Reply Last reply Reply Quote 0
            • JaredBuschJ
              JaredBusch @gjacobse
              last edited by

              @gjacobse said in ScreenConnect on CentOS is sluggish:

              @JaredBusch said in ScreenConnect on CentOS is sluggish:

              @gjacobse said in ScreenConnect on CentOS is sluggish:

              @JaredBusch

              Question on that - Do you have the system do DB maintenance?!

              That answer, is no. My bad on that.

              It wasn't set on the NTG system at first either. But once set, and allowed to cycle it's kept the DB in check. If you set today, it's likely that it won't process until the next run time, which will be Tuesday Night / Wednesday Morning....

              At least that is what SC Support explained to me.

              I have a clean Session.db, so nothing there now anyway. Debating if I should put the old one back and let this run.

              1 Reply Last reply Reply Quote 0
              • JaredBuschJ
                JaredBusch
                last edited by JaredBusch

                ok, just moved the new session DB out and copied the old one back in. going to setup the maintenance task and see what happens.

                [root@bnasc ~]# ls -l /opt/screenconnect/App_Data/
                total 635964
                -rw-r--r--. 1 root root       803 Nov  4 12:41 ExtensionConfiguration.xml
                drwxr-xr-x. 2 root root        42 Jan 31 17:59 Helper
                -rw-r--r--. 1 root root       381 Aug 10 01:05 License.xml
                -rw-r--r--. 1 root root     16220 Jan 31 17:59 Role.xml
                -rw-r--r--. 1 root root 322928640 Feb  6 17:03 Session.db
                -rw-r--r--. 1 root root 322928640 Feb  6 11:29 Session.db.2017.02.06.old
                -rw-r--r--. 1 root root   1163264 Feb  6 16:30 Session.db.2017.02.06.new
                -rw-r--r--. 1 root root     32768 Feb  6 17:00 Session.db-shm
                -rw-r--r--. 1 root root   4132392 Feb  6 17:00 Session.db-wal
                -rw-r--r--. 1 root root      1045 Jul  1  2014 SessionEventTrigger.xml
                -rw-r--r--. 1 root root      3250 Jun 21  2016 SessionGroup.xml
                drwxr-xr-x. 2 root root        86 Jan 31 18:09 Toolbox
                -rw-r--r--. 1 root root      6001 Feb  6 12:07 User.xml
                
                1 Reply Last reply Reply Quote 1
                • JaredBuschJ
                  JaredBusch
                  last edited by JaredBusch

                  big ba-da boom

                  0_1486422455491_upload-f82269d1-a1fe-4d52-bdfc-4ec92b42ad64

                  1 Reply Last reply Reply Quote 1
                  • JaredBuschJ
                    JaredBusch
                    last edited by

                    Put the new one back and it start up just fine /sigh

                    1 Reply Last reply Reply Quote 1
                    • gjacobseG
                      gjacobse
                      last edited by

                      Well at least the new one is still okay... would be a major pain otherwise.

                      1 Reply Last reply Reply Quote 0
                      • JaredBuschJ
                        JaredBusch
                        last edited by

                        A week later, the database file is still small with 157 devices having reported back in.

                        -rw-r--r--. 1 root root   1163264 Feb  6 16:30 Session.db.2017.02.06.new
                        -rw-r--r--. 1 root root 322928640 Feb  6 11:29 Session.db.2017.02.06.old
                        -rw-r--r--. 1 root root   1654784 Feb 11 16:03 Session.db.2017.02.11.new
                        

                        Time to test the backup and contact support if it doesn't load.

                        1 Reply Last reply Reply Quote 1
                        • JaredBuschJ
                          JaredBusch
                          last edited by

                          Worked perfectly this time..

                          0_1486850965597_upload-c6d2970b-3c2b-4e43-8c70-b0ee87330a9c

                          1 Reply Last reply Reply Quote 0
                          • JaredBuschJ
                            JaredBusch
                            last edited by

                            Going to run the DB maintenance on this and see what happens.

                            You can only choose one thehour inthe drop down, so the next hour is 17:00.
                            Currently 16:12 here.

                            0_1486851135047_upload-f5ed5085-c033-4287-af54-a559f84760da

                            1 Reply Last reply Reply Quote 0
                            • JaredBuschJ
                              JaredBusch
                              last edited by

                              Well, that made just a small amount of difference..

                              -rw-r--r--. 1 root root 322928640 Feb  6 11:29 Session.db.2017.02.06.old
                              -rw-r--r--. 1 root root   4034560 Feb 11 17:00 Session.db
                              
                              1 Reply Last reply Reply Quote 2
                              • JaredBuschJ
                                JaredBusch
                                last edited by

                                Little follow up to this as SC on CentOS was discussed in abother thread.. DB size is still small.

                                [root@bnasc ~]# ls -l /opt/screenconnect/App_Data/Session.db
                                -rw-r--r--. 1 root root 46764032 Jan 26 12:30 /opt/screenconnect/App_Data/Session.db
                                
                                1 Reply Last reply Reply Quote 3
                                • 1
                                • 2
                                • 2 / 2
                                • First post
                                  Last post