Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: HOP_LOG_LEVEL=Minimal not considered on Kubernetes environment #4849

Open
bozhidarpamukchiyski opened this issue Jan 30, 2025 · 0 comments

Comments

@bozhidarpamukchiyski
Copy link

Apache Hop version?

2.9.0

Java version?

17

Operating system

Docker

What happened?

Hello,

Simillar issue was faced and discussed a bit in that ticket:
#4205

The issue is when the APACHE_HOP_LEVEL=Minimal after triggering the server using the AsyncWebService the log are always on basic level.
As @hansva mentioned the running scripts need some adjustments. I have created a custom Docker image that extends the parent Docker image and executes custom run.sh, hop-server.sh and load-and-execute.sh.

In my custom-hop-server.sh I've added the following logging to see what parameters are passed:
`echo "HOP_EXEC_OPTIONS: ${HOP_EXEC_OPTIONS}"
echo "Arguments received by hop-server.sh: $@"

"${_HOP_JAVA}" ${HOP_OPTIONS} -Djava.library.path="${LIBPATH}" -classpath "${CLASSPATH}" org.apache.hop.www.HopServer "$@"
EXITCODE=$?`

According to the log the parameters are correctly passed:

HOP_OPTIONS: -XX:+AggressiveHeap -DHOP_AUDIT_FOLDER=./audit -DHOP_CONFIG_FOLDER=/files/etl -DHOP_SHARED_JDBC_FOLDERS=/files/config/plugins/database_drivers -DHOP_PLATFORM_RUNTIME=Server -DHOP_AUTO_CREATE_CONFIG=Y -DHOP_PLATFORM_OS=Linux --add-opens java.xml/jdk.xml.internal=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.base/java.lang.reflect=ALL-UNNAMED --add-opens java.base/java.io=ALL-UNNAMED --add-opens java.base/java.net=ALL-UNNAMED --add-opens java.base/java.nio=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.util.concurrent=ALL-UNNAMED --add-opens java.base/java.util.concurrent.atomic=ALL-UNNAMED --add-opens java.base/sun.nio.ch=ALL-UNNAMED --add-opens java.base/sun.nio.cs=ALL-UNNAMED --add-opens java.base/sun.security.action=ALL-UNNAMED --add-opens java.base/sun.util.calendar=ALL-UNNAMED --add-opens java.security.jgss/sun.security.krb5=ALL-UNNAMED --add-exports java.base/sun.nio.ch=ALL-UNNAMED
Arguments received by hop-server.sh: --level=Minimal --project=hop-finalize /tmp/hop-server.xml
2025/01/30 20:34:36 - HopServer - Enabling project 'hop-finalize'
2025/01/30 20:34:36 - HopServer - Installing timer to purge stale objects after 1440 minutes.
2025/01/30 20:34:37 - HopServer - Created listener for webserver @ address : 0.0.0.0:8081
2025/01/30 20:35:41 - run - Start of workflow execution
2025/01/30 20:35:41 - run - Starting action [Set variables]
2025/01/30 20:35:41 - Set variables - Using run configuration [local]
2025/01/30 20:35:41 - set-variables - Executing this pipeline using the Local Pipeline Engine with run configuration 'local'
2025/01/30 20:35:41 - set-variables - Execution started for pipeline [set-variables]

But the log is still on Basic level, i've did some research on HopServer.java, LogLevel.java classes but i cannot find the issue

Thanks in advance

Issue Priority

Priority: 3

Issue Component

Component: Hop Server

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant