10 Replies Latest reply on Feb 20, 2017 8:24 AM by Andrew Waters

    Remote access failed: Windows Proxy overloaded

      Share This:

      The subjected error message is observed when performing a credential test. What is this error and how can it be corrected.

        • 1. Re: Remote access failed: Windows Proxy overloaded
          Andrew Waters

          A proxy will report it is overloaded if there are too many things being currently run on it.

           

          It is possible to increase the number of concurrent requests though this is not normally a good idea. Better would be to have multiple proxies in a pool to distribute the work. If you do not think that it is running much then you need to look at what it thinks it is doing by examining the proxy logs.

          • 2. Re: Remote access failed: Windows Proxy overloaded

            Thanks Andrew. In this case re-booting the windows server hosting the proxy helped restoring successful communication once again.

            • 3. Re: Remote access failed: Windows Proxy overloaded

              Hi Team,

               

              Customer is getting an the proxy overloaded error when ever the customer installs a windows proxy. Last time when the issue occurred , it was resolved when we restarted the  proxy machine. Customer is not happy about rebooting the proxy which is a workaround but he needs to find the root cause. Now Customer had installed a new Windows proxy server to the proxy pool, and facing the same overload issue.

               

              In the log we can see below errors occurring multiple times. This error might kept the proxy busy and possibly the root cause of this issue.

               

               

              "File "discovery\slave\manager\workers.pyo", line 930, in _createWorker

                File "stubs\discovery_idl.pyo", line 1358, in loadConfiguration

              TRANSIENT: CORBA.TRANSIENT(omniORB.TRANSIENT_ConnectFailed, CORBA.COMPLETED_NO)

              3912: 2015-06-24 00:13:58,986: discovery.slave.manager.workers: DEBUG: Converting IOR:010000002f00000049444c3a746964657761792e636f6d2f446973636f76657279434f5242412f536c617665576f726b65723a312e300000010000000000000060000000010102000a0000003132372e302e302e3100c0db0e000000fed693895500001114000000000000000200000000000000080000000100000000545441010000001c00000001000000010001050100000001000105090101000100000009010100 to worker

              3912: 2015-06-24 00:13:58,986: discovery.slave.manager.workers: DEBUG: Load worker configuration.

              3912: 2015-06-24 00:13:59,003: discovery.slave.manager.workers: ERROR: Unable to upload configuration to worker IOR:010000002f00000049444c3a746964657761792e636f6d2f446973636f76657279434f5242412f536c617665576f726b65723a312e300000010000000000000060000000010102000a0000003132372e302e302e3100c0db0e000000fed693895500001114000000000000000200000000000000080000000100000000545441010000001c00000001000000010001050100000001000105090101000100000009010100

              Traceback (most recent call last)"

               

              I tried to find the File "discovery\slave\manager\workers.pyo" and  File "stubs\discovery_idl.pyo" on the Proxy server, but I can't find them.

               

              When I tired to reproduce the issue in my lab, i was not getting any error (overload or CORBA error). What could be the possible root cause?

               

              Regards,

              JayMurali

              • 4. Re: Remote access failed: Windows Proxy overloaded
                Andrew Waters

                For some reason the controlling process cannot initialise the worker process.

                 

                Is there any discoproxy_worker_*.log file? Does it contain anything?

                • 5. Re: Remote access failed: Windows Proxy overloaded

                  Hi Andrew,

                   

                  I didn't notice any useful lines indiscoproxy_worker_*.log file. Below are the last few lines of the log.

                   

                  3216: 2015-07-17 14:55:06,316: common.configuration: INFO: Consuming --parent-pid argument: 4740

                  3216: 2015-07-17 14:55:06,316: discovery.slave.worker.servants: INFO: Proxy running as user WORKGROUP\PUATWADDMAPP04$

                  3216: 2015-07-17 14:55:06,394: discovery.slave.worker.servants: INFO: Sending worker object reference to Proxy manager: IOR:010000002f00000049444c3a746964657761792e636f6d2f446973636f76657279434f5242412f536c617665576f726b65723a312e300000010000000000000060000000010102000a0000003132372e302e302e310014e50e000000fedab4a855000009ac000000000000000200000000000000080000000100000000545441010000001c00000001000000010001050100000001000105090101000100000009010100

                  3216: 2015-07-17 14:55:06,394: discovery.slave.worker.options: INFO: My IP addresses: 172.31.168.220,172.31.95.45,127.0.0.1,172.31.247.69

                  3216: 2015-07-17 14:55:06,394: common.server: INFO: Install SIGTERM handler.

                   

                  Regards,

                  JayMurali

                  • 6. Re: Remote access failed: Windows Proxy overloaded
                    Andrew Waters

                    One of these logs appears to be from running in June and the other July.

                    • 7. Re: Remote access failed: Windows Proxy overloaded

                      Yes, We reproduced the issue and got the logs again . same error in tw_svc_winproxy log when we got the lines from the  discoproxy_worker_*.log.

                       

                      4216: 2015-07-17 14:15:53,095: discovery.slave.manager.workers: ERROR: Unable to upload configuration to worker IOR:010000002f00000049444c3a746964657761792e636f6d2f446973636f76657279434f5242412f536c617665576f726b65723a312e300000010000000000000060000000010102000a0000003132372e302e302e3100a2e30e000000fea9aba85500000bc0000000000000000200000000000000080000000100000000545441010000001c00000001000000010001050100000001000105090101000100000009010100

                      Traceback (most recent call last):

                        File "discovery\slave\manager\workers.pyo", line 930, in _createWorker

                        File "stubs\discovery_idl.pyo", line 1358, in loadConfiguration

                      TRANSIENT: CORBA.TRANSIENT(omniORB.TRANSIENT_ConnectFailed, CORBA.COMPLETED_NO)

                      4216: 2015-07-17 14:16:08,642: discovery.slave.manager.workers: ERROR: Unable to upload configuration to worker IOR:010000002f00000049444c3a746964657761792e636f6d2f446973636f76657279434f5242412f536c617665576f726b65723a312e300000010000000000000060000000010102000a0000003132372e302e302e3100a4e30e000000feb8aba855000010d8000000000000000200000000000000080000000100000000545441010000001c00000001000000010001050100000001000105090101000100000009010100

                      Traceback (most recent call last):

                      • 8. Re: Remote access failed: Windows Proxy overloaded
                        Andrew Waters

                        Do you have an example where the IOR logged does work on the same system?

                        • 9. Re: Remote access failed: Windows Proxy overloaded
                          Somnath Shilimkar

                          Hi Diwakar,

                           

                          Have you got resolution for this error ?

                           

                          I am facing same issue in our environment. there are no discovery runs in place. we have less than 200 servers in total. still when i put any credential test on windows proxy it shows this error. "Remote access failed: Windows Proxy Overloaded"

                           

                          Thanks in Adavance,

                          Somnath.

                          • 10. Re: Remote access failed: Windows Proxy overloaded
                            Andrew Waters

                            Are you seeing the same error in the logs on the proxy - that it is unable to create a worker?