Announcement

Collapse
No announcement yet.

100% CPU usage "java -Djava.net" (reddit duplicate)

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Originally posted by support200 View Post
    I asked you that what is your DNS server while your NxProxy running and what do you see in the log file already. Upload your log file and see if your DNS settings changed while NxProxy running.
    Here is the log file!
    Attached Files

    Comment


    • #17
      Originally posted by support200 View Post
      Did you run NxProxy on CMD with your login account? If you talk about NxProxy as Windows service, it's not your login account. It runs under another account.
      No, I just log into my Windows Administrator account, and in this account, there are no GPOS for my Windows admin user and even without GPOS (group policies), the POWERSHELL service still takes up a lot of CPU. This service just stops taking up absurdly, after I disable the service called NXPROXY inside the windows services.msc panel as an admin

      Comment


      • #18
        Your service is not running with Admin account. It runs with another account. What's your DNS server IP? It tries to change your DNS settings every 15 seconds,

        Code:
        NFO [11-17 16:28:42] - LocalResolver.findLocalDnsIpByDhcp, New local DNS server = 8.8.8.8.
        INFO [11-17 16:28:43] - HandyMan.hijackDns, Updating DNS settings on Windows.
        Try this command on your CMD while your NxProxy running,

        Code:
        nslookup google.com
        And show me the result. Run the command while your NxProxy running.

        Comment


        • #19
          Why don't you just separate your system from Active Directory. I actually don't understand why you run NxFilter on cloud while you have AD in your local network. NxProxy is for mobile workers. It shouldn't be in AD. If you want to run it inside AD, it should be able to change its system DNS settings. And you keep saying that you logged-in as Admin but your NxProxy is already running before you logged-in. That's because it's a Windows service. It's not related to your login account.
          Last edited by support200; 11-19-2021, 02:05 AM.

          Comment


          • #20
            Windows services are running under Local System account at default. You can change it if you want to on the service properties page.

            Comment


            • #21
              This is an older answer from me,

              You were talking about NxFilter on Ubuntu. You run your VMWare on your Windows workstation and you run NxProxy there? NxProxy tries to change your DNS settings every 15 seconds. And it uses Powershell script there. Did you lock your DNS settings somehow? Then unlock it for NxProxy to change it. Or you can change your DNS server settings to point 127.0.0.1 by yourself.
              What did I tell you? If it can't change it, try to change it by yourself. Change your DNS server IP to 127.0.0.1.

              Comment


              • #22
                Originally posted by support200 View Post
                Your service is not running with Admin account. It runs with another account. What's your DNS server IP? It tries to change your DNS settings every 15 seconds,

                Code:
                NFO [11-17 16:28:42] - LocalResolver.findLocalDnsIpByDhcp, New local DNS server = 8.8.8.8.
                INFO [11-17 16:28:43] - HandyMan.hijackDns, Updating DNS settings on Windows.
                Try this command on your CMD while your NxProxy running,

                Code:
                nslookup google.com
                And show me the result. Run the command while your NxProxy running.
                Here is the result attached.
                Attached Files

                Comment


                • #23
                  Originally posted by support200 View Post
                  Why don't you just separate your system from Active Directory. I actually don't understand why you run NxFilter on cloud while you have AD in your local network. NxProxy is for mobile workers. It shouldn't be in AD. If you want to run it inside AD, it should be able to change its system DNS settings. And you keep saying that you logged-in as Admin but your NxProxy is already running before you logged-in. That's because it's a Windows service. It's not related to your login account.
                  I am not using active directory on this network.I have deployed the NXFILTER server in the cloud, precisely to not have costs in setting up and taking care of a physical server, with security, heating ...
                  The public address of my NXFILTER server is 186.226.57.248
                  Last edited by marcelofares; 11-19-2021, 01:45 PM.

                  Comment


                  • #24
                    Originally posted by marcelofares View Post

                    Here is the log file!
                    Have you seen these logs? Anything to say about this?

                    Comment


                    • #25
                      I saw the log file and it tries to update your DNS settings. When you get that capture image, do you see that 100% CPU load?

                      Comment


                      • #26
                        Originally posted by support200 View Post
                        I saw the log file and it tries to update your DNS settings. When you get that capture image, do you see that 100% CPU load?
                        Yes, I always have very high CPU load with this WINDOWS POWERSHELL process consuming a lot, and when I disable the NXPROXY service that runs in the background, everything goes back to normal and no excessive load.

                        Comment


                        • #27
                          I attached a new one with more log messages. Try to run it on foreground with your Admin account.

                          1. Stop your service.

                          2. Copy the attached nxproxy.jar to C:\Program Files (x86)\nxproxy\

                          3. Run C:\Program Files (x86)\nxproxy\bin\startup.bat

                          And upload your log file after 5 minutes.
                          Attached Files

                          Comment


                          • #28
                            And capture that nslookup result this time as well.

                            Comment


                            • #29
                              It may not be able to detect your DNS settings changed for some reason. We will get you another one doing the checking process in a different way. While you waiting, you can do the test with the one we uploaded already. We need to confirm which is the real problem first.

                              Comment


                              • #30
                                Originally posted by support200 View Post
                                I attached a new one with more log messages. Try to run it on foreground with your Admin account.

                                1. Stop your service.

                                2. Copy the attached nxproxy.jar to C:\Program Files (x86)\nxproxy\

                                3. Run C:\Program Files (x86)\nxproxy\bin\startup.bat

                                And upload your log file after 5 minutes.


                                Just performed the procedure you instructed me to do.

                                What I noticed = The high powershell consumption is not constant anymore, sometimes the process goes to a peak, but there is not every moment. Here are the prints and logs of what I managed to get.
                                Note - startup.bat was running (open without closing).
                                Attached Files

                                Comment


                                • support200
                                  support200 commented
                                  Editing a comment
                                  It's because now it can change your DNS settings and can detect the change. In the log file,

                                  INFO [11-19 18:57:44] - HandyMan.isDnsHijacked, 192.168.10.1
                                  INFO [11-19 18:57:44] - HandyMan.hijackDns, Updating DNS settings on Windows.
                                  INFO [11-19 18:57:47] - HandyMan.isDnsHijacked, 127.0.0.1
                              Working...
                              X