Can anyone help me with package size of a process which can be uploaded to Orchestrator

Help Automation Suite
,
1

i have a script which auto upload the package into orchestrator but from last few builds package is not being pushed to orchestrator, so I am curious to know what is idle size of package which can be uploaded to Orchestrator.
Previously in standalone it was approx. 30 MB but I have not found any thing same in Automation Suite.

2

@Divyanshu_Divyanshu

Please check this

You can modify as well if needed

Cheers

3

Hello @Anil_G
Thank you for the link
I have gone through it but as on the website it is written it is for the Standalone.
Is this same apply for Automation Suite as well?

4

@Divyanshu_Divyanshu,

Best practice would be keeping the package size as low as possible. If it’s growing bigger then it may affect the bot performence as well.

5

Hi @Divyanshu_Divyanshu

You can increase this limit

How To Increase The Size Limit Of Project To Be Uploaded In Orchestrator - News / Knowledge Base - UiPath Community Forum

Hope this helps :slight_smile:

6

Thank you @AJ_Ask
Could you please provide the steps relevant to Automation Suite Hosted on Linux as we are not using IIS.
It will be helpful.

7

I agree with You @ashokkarale but when I am checking the logs I can see no failure in building/packaging or even upload API has not given any error but when i logged in Orchestrator it is not there.
So i was looking for some guideline if I am missing something.

8

To configure UiPath Automation Suite hosted on Linux (without IIS) and ensure successful package uploads to Orchestrator, you’ll typically be using Nginx as the reverse proxy. Here’s a detailed step-by-step guide to address potential issues, especially with larger package uploads:

Steps to Configure Nginx for Larger File Uploads:

  1. Locate Nginx Configuration File:

    • The Nginx configuration file is usually located at:
      • /etc/nginx/nginx.conf (global configuration)
      • /etc/nginx/sites-available/default (or specific site config file)

  2. Increase client_max_body_size:

    • This directive defines the maximum allowed size of the client request body. To handle larger file uploads (for instance, a 30MB package), you’ll need to increase this limit.

    • Open your Nginx configuration file for editing. For example:

      sudo nano /etc/nginx/nginx.conf

    • Look for the http or server block and add the client_max_body_size directive:

      http {
    ...
    client_max_body_size 100M;  # This sets the upload size limit to 100MB
    ...
}

    • If you’re using a specific site configuration file, add the same directive in the appropriate server block.
      Example for a site-specific config:

      server {
    ...
    client_max_body_size 100M;
    ...
}

  3. Restart Nginx to Apply Changes:

    • After modifying the Nginx configuration, restart the service to apply the changes:
      sudo systemctl restart nginx

  4. Verify Nginx Logs:

    • Check the Nginx error logs to ensure no errors related to package uploads are being triggered:
      sudo tail -f /var/log/nginx/error.log

  5. Check Orchestrator Logs:

    • Orchestrator logs are also important to verify if there are any application-specific errors related to the upload. Logs can typically be found under:
      /var/log/uipath/orchestrator/

  6. Verify Other System Configurations:

    • Ensure that the Linux system’s file upload and network configurations allow for larger files. Check for any other potential restrictions in place (e.g., firewalls, network timeouts).
    • You might also need to verify any reverse proxy settings between Nginx and the Orchestrator server.

Steps to Troubleshoot Package Upload Issues:

  1. Check the Upload Process:

    • If the upload fails, examine the Orchestrator logs for any detailed error messages that indicate the cause of the failure.

  2. Verify Orchestrator Configuration:

    • Ensure that your Orchestrator settings do not impose a file size limit for package uploads. This is usually managed automatically by Orchestrator but can depend on your specific setup.

  3. Check Available Disk Space:

    • Verify that the Orchestrator server has enough disk space to handle large package uploads. If the server runs out of space, it will not be able to accept the uploads.
      df -h

  4. Test Package Uploads via the Orchestrator Web UI:

    • Try uploading a smaller package via the Orchestrator web UI to check if it’s a general upload issue or specific to certain package sizes.

  5. Check the Network:

    • Ensure there are no network issues or firewalls blocking the upload process, particularly if you’re using reverse proxies or VPNs.

Example of Nginx Configuration Changes:

Here’s an example of how your Nginx config might look after applying the changes:

http {
    ...
    client_max_body_size 100M;  # Increase to allow larger uploads
    ...
}

server {
    listen 80;
    server_name orchestrator.example.com;

    location / {
        proxy_pass http://127.0.0.1:5000;  # Example proxy pass to Orchestrator
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

After making these changes and restarting Nginx, your Automation Suite should be able to handle larger package uploads to Orchestrator without issues.

9

Hi @Divyanshu_Divyanshu

Best option would be raise the support ticket to UiPath. They will help you out.

Add Support Request | Customer Portal

Hope this helps :slight_smile:

10

With Automation Suite, there is a lot of options and therefore a lot of “it depends”.
One good first place to look for example:
Packages would end up in the Object Store, so if you have configured an external one (such as S3) you may want to take a look at its configuration to see how large the uploads are allowed to be there.