SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-08-01 18:28:45 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Stirling-PDF installation Script failed with error #1180

New Issue
Closed
opened 2025-11-20 05:05:49 -05:00 by saavagebueno · 3 comments
saavagebueno commented 2025-11-20 05:05:49 -05:00
Owner
Copy Link

Originally created by @liprox on GitHub (May 28, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Stirling-PDF

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/stirling-pdf.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📝 Provide a clear and concise description of the issue.

HI,

Today I wanted to set up the corresponding LXC container using the "Sterling-PDF" script:
''bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/stirling-pdf.sh)" ''.

Proxmox is version 8.4.1.

The installation aborts with the following error message:

⠼Trigger für libc-bin (2.36-9+deb12u10) werden verarbeitet ...
✔️ Installed Language Packs
⠦Downloading https://services.gradle.org/distributions/gradle-8.14-all.zip
⠧...100%.....
⠇
Welcome to Gradle 8.14!

Here are the highlights of this release:

  • Java 24 support
  • GraalVM Native Image toolchain selection
  • Enhancements to test reporting
  • Build Authoring improvements

For more details see https://docs.gradle.org/8.14/release-notes.html

⠋Starting a Gradle Daemon (subsequent builds will be faster)

Task :compileJava
Note: /opt/jbig2enc/Stirling-PDF-0.46.2/src/main/java/stirling/software/SPDF/controller/api/security/ValidateSignatureController.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
<=
Task :compileTestJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
<=OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended
<=
Task :test

GeneralUtilsAdditionalTest > testFormatBytes() FAILED
org.opentest4j.AssertionFailedError at GeneralUtilsAdditionalTest.java:22
<=
309 tests completed, 1 failed
<=

Task :test FAILED

[Incubating] Problems report is available at: file:///opt/jbig2enc/Stirling-PDF-0.46.2/build/reports/problems/problems-report.html

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ':test'.

There were failing tests. See the report at: file:///opt/jbig2enc/Stirling-PDF-0.46.2/build/reports/tests/test/index.html

  • Try:

Run with --scan to get full insights.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.14/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 2m 18s
12 actionable tasks: 11 executed, 1 up-to-date
⠧
[ERROR] in line 83: exit code 0: while executing command $STD ./gradlew build
/dev/fd/63: Zeile 74: SPINNER_PID ist nicht gesetzt.
⠸

The script is probably outdated. I suspect it is no longer compatible with the current version of Proxmox.

regards,
gerd

🔄 Steps to reproduce the issue.

Step 1:
on Proxmox command line (in Web GUI):
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/stirling-pdf.sh)"
Step 2:
default settings
Step 3:
the Error above

❌ Paste the full error output (if available).

⠼Trigger für libc-bin (2.36-9+deb12u10) werden verarbeitet ...
✔️ Installed Language Packs
⠦Downloading https://services.gradle.org/distributions/gradle-8.14-all.zip
⠧...100%.....
⠇
Welcome to Gradle 8.14!

Here are the highlights of this release:

  • Java 24 support
  • GraalVM Native Image toolchain selection
  • Enhancements to test reporting
  • Build Authoring improvements

For more details see https://docs.gradle.org/8.14/release-notes.html

⠋Starting a Gradle Daemon (subsequent builds will be faster)

Task :compileJava
Note: /opt/jbig2enc/Stirling-PDF-0.46.2/src/main/java/stirling/software/SPDF/controller/api/security/ValidateSignatureController.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
<=
Task :compileTestJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
<=OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended
<=
Task :test

GeneralUtilsAdditionalTest > testFormatBytes() FAILED
org.opentest4j.AssertionFailedError at GeneralUtilsAdditionalTest.java:22
<=
309 tests completed, 1 failed
<=

Task :test FAILED

[Incubating] Problems report is available at: file:///opt/jbig2enc/Stirling-PDF-0.46.2/build/reports/problems/problems-report.html

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ':test'.

There were failing tests. See the report at: file:///opt/jbig2enc/Stirling-PDF-0.46.2/build/reports/tests/test/index.html

  • Try:

Run with --scan to get full insights.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.14/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 2m 18s
12 actionable tasks: 11 executed, 1 up-to-date
⠧
[ERROR] in line 83: exit code 0: while executing command $STD ./gradlew build
/dev/fd/63: Zeile 74: SPINNER_PID ist nicht gesetzt.
⠸

🖼️ Additional context (optional).

No response

Originally created by @liprox on GitHub (May 28, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Stirling-PDF ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/stirling-pdf.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📝 Provide a clear and concise description of the issue. HI, Today I wanted to set up the corresponding LXC container using the "Sterling-PDF" script: ''bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/stirling-pdf.sh)" ''. Proxmox is version 8.4.1. The installation aborts with the following error message: --------------------------------------------------------- ⠼Trigger für libc-bin (2.36-9+deb12u10) werden verarbeitet ... ✔️ Installed Language Packs ⠦Downloading https://services.gradle.org/distributions/gradle-8.14-all.zip ⠧...100%..... ⠇ Welcome to Gradle 8.14! Here are the highlights of this release: - Java 24 support - GraalVM Native Image toolchain selection - Enhancements to test reporting - Build Authoring improvements For more details see https://docs.gradle.org/8.14/release-notes.html ⠋Starting a Gradle Daemon (subsequent builds will be faster) > Task :compileJava Note: /opt/jbig2enc/Stirling-PDF-0.46.2/src/main/java/stirling/software/SPDF/controller/api/security/ValidateSignatureController.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. <= > Task :compileTestJava Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. <=OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended <= > Task :test GeneralUtilsAdditionalTest > testFormatBytes() FAILED org.opentest4j.AssertionFailedError at GeneralUtilsAdditionalTest.java:22 <= 309 tests completed, 1 failed <= > Task :test FAILED [Incubating] Problems report is available at: file:///opt/jbig2enc/Stirling-PDF-0.46.2/build/reports/problems/problems-report.html FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':test'. > There were failing tests. See the report at: file:///opt/jbig2enc/Stirling-PDF-0.46.2/build/reports/tests/test/index.html * Try: > Run with --scan to get full insights. Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. For more on this, please refer to https://docs.gradle.org/8.14/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. BUILD FAILED in 2m 18s 12 actionable tasks: 11 executed, 1 up-to-date ⠧ [ERROR] in line 83: exit code 0: while executing command $STD ./gradlew build /dev/fd/63: Zeile 74: SPINNER_PID ist nicht gesetzt. ⠸ --------------------------------------------------------- The script is probably outdated. I suspect it is no longer compatible with the current version of Proxmox. regards, gerd ### 🔄 Steps to reproduce the issue. Step 1: on Proxmox command line (in Web GUI): bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/stirling-pdf.sh)" Step 2: default settings Step 3: the Error above ### ❌ Paste the full error output (if available). ⠼Trigger für libc-bin (2.36-9+deb12u10) werden verarbeitet ... ✔️ Installed Language Packs ⠦Downloading https://services.gradle.org/distributions/gradle-8.14-all.zip ⠧...100%..... ⠇ Welcome to Gradle 8.14! Here are the highlights of this release: - Java 24 support - GraalVM Native Image toolchain selection - Enhancements to test reporting - Build Authoring improvements For more details see https://docs.gradle.org/8.14/release-notes.html ⠋Starting a Gradle Daemon (subsequent builds will be faster) > Task :compileJava Note: /opt/jbig2enc/Stirling-PDF-0.46.2/src/main/java/stirling/software/SPDF/controller/api/security/ValidateSignatureController.java uses unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. <= > Task :compileTestJava Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. <=OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended <= > Task :test GeneralUtilsAdditionalTest > testFormatBytes() FAILED org.opentest4j.AssertionFailedError at GeneralUtilsAdditionalTest.java:22 <= 309 tests completed, 1 failed <= > Task :test FAILED [Incubating] Problems report is available at: file:///opt/jbig2enc/Stirling-PDF-0.46.2/build/reports/problems/problems-report.html FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':test'. > There were failing tests. See the report at: file:///opt/jbig2enc/Stirling-PDF-0.46.2/build/reports/tests/test/index.html * Try: > Run with --scan to get full insights. Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. For more on this, please refer to https://docs.gradle.org/8.14/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. BUILD FAILED in 2m 18s 12 actionable tasks: 11 executed, 1 up-to-date ⠧ [ERROR] in line 83: exit code 0: while executing command $STD ./gradlew build /dev/fd/63: Zeile 74: SPINNER_PID ist nicht gesetzt. ⠸ ### 🖼️ Additional context (optional). _No response_
saavagebueno added the not a script issueexternal labels 2025-11-20 05:05:49 -05:00
saavagebueno commented 2025-11-20 05:05:50 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (May 28, 2025):

Script work fine

Image

3 issues it could be, since it comes from gradle itself:

  1. wrong locale (en_US.UTF-8 vs de_DE.UTF-8)
  2. wrong decimal separator 1.23 vs 1,23
  3. wrong encoding UTF-8 vs C

You should probably report this to the Stirling PDF repo, as we have no influence on the gradle builds.

@MickLesk commented on GitHub (May 28, 2025): Script work fine ![Image](https://github.com/user-attachments/assets/04962d74-8cf8-4434-8fc7-a9aed1d141fa) 3 issues it could be, since it comes from gradle itself: 1. wrong locale (en_US.UTF-8 vs de_DE.UTF-8) 2. wrong decimal separator 1.23 vs 1,23 3. wrong encoding UTF-8 vs C You should probably report this to the Stirling PDF repo, as we have no influence on the gradle builds.
saavagebueno commented 2025-11-20 05:05:50 -05:00
Author
Owner
Copy Link

@liprox commented on GitHub (May 28, 2025):

Hi MickLesk,

thank you for your answer.

I make a new try. Now with en_US.UTF-8 instead of de_DE.UTF-8. (default)
But now I get also an ERROR:

''
⚙️ Using Default Settings on node fcprox
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Unprivileged
💾 Disk Size: 8 GB
🧠 CPU Cores: 2
🛠️ RAM Size: 2048 MiB
🆔 Container ID: 104
🚀 Creating a Stirling-PDF LXC using the above default settings

✔️ Using vz-r5pool for Template Storage.
✔️ Using r10pool-zfs for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Template is ready to use.
✔️ LXC Container 104 was successfully created.
✔️ Started LXC Container
✔️ Set up Container OS
✔️ Network Connected: 172.21.8.153
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ DNS Resolved github.com to 140.82.121.3
✔️ Updated Container OS
✔️ Core dependencies installed
✔️ Installed Dependencies
✔️ Installed LibreOffice Components
✔️ Installed Python Dependencies
✔️ Installed Azul Zulu
✔️ Installed JBIG2
✔️ Installed Language Packs
⠋ Installing Stirling-PDF (Additional Patience)
[ERROR] in line 51: exit code 0: while executing command "$@" > /dev/null 2>&1
curl: (22) The requested URL returned error: 400
/dev/fd/63: Zeile 74: SPINNER_PID ist nicht gesetzt. ''

With:
"... report this to the Stirling PDF repo, as we have no influence on the gradle builds."
you mean this site?:
https://github.com/Stirling-Tools/Stirling-PDF/issues

thank you and
regards
gerd

@liprox commented on GitHub (May 28, 2025): Hi MickLesk, thank you for your answer. I make a new try. Now with en_US.UTF-8 instead of de_DE.UTF-8. (default) But now I get also an ERROR: '' ⚙️ Using Default Settings on node fcprox 🖥️ Operating System: debian 🌟 Version: 12 📦 Container Type: Unprivileged 💾 Disk Size: 8 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🆔 Container ID: 104 🚀 Creating a Stirling-PDF LXC using the above default settings ✔️ Using vz-r5pool for Template Storage. ✔️ Using r10pool-zfs for Container Storage. ✔️ Updated LXC Template List ✔️ LXC Template is ready to use. ✔️ LXC Container 104 was successfully created. ✔️ Started LXC Container ✔️ Set up Container OS ✔️ Network Connected: 172.21.8.153 ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ DNS Resolved github.com to 140.82.121.3 ✔️ Updated Container OS ✔️ Core dependencies installed ✔️ Installed Dependencies ✔️ Installed LibreOffice Components ✔️ Installed Python Dependencies ✔️ Installed Azul Zulu ✔️ Installed JBIG2 ✔️ Installed Language Packs ⠋ Installing Stirling-PDF (Additional Patience) [ERROR] in line 51: exit code 0: while executing command "$@" > /dev/null 2>&1 curl: (22) The requested URL returned error: 400 /dev/fd/63: Zeile 74: SPINNER_PID ist nicht gesetzt. '' With: "... report this to the Stirling PDF repo, as we have no influence on the gradle builds." you mean this site?: https://github.com/Stirling-Tools/Stirling-PDF/issues thank you and regards gerd
saavagebueno commented 2025-11-20 05:05:50 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (May 28, 2025):

yep, please there.

@MickLesk commented on GitHub (May 28, 2025): yep, please there.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label external not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1180
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?