Your message dated Wed, 26 May 2021 20:23:24 +0300
with message-id <[email protected]>
and subject line Re: Bug#989142: logstash: Illegal reflective access by
org.jruby.util.SecurityHelper
has caused the Debian Bug report #989142,
regarding logstash: Illegal reflective access by org.jruby.util.SecurityHelper
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
989142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989142
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: logstash
Version: 1:6.8.16-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Update deb package
* What exactly did you do (or not do) that was effective (or
ineffective)?
apt upgrade
* What was the outcome of this action?
Setting up logstash (1:6.8.16-1) ...
Using provided startup.options file: /etc/logstash/startup.options
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jruby.util.SecurityHelper to field
java.lang.reflect.Field.modifiers
WARNING: Please consider reporting this to the maintainers of
org.jruby.util.SecurityHelper
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/pleaserun-0.0.31/lib/pleaserun/platform/base.rb:112:
warning: constant ::Fixnum is deprecated
Successfully created system startup script for Logstash
* What outcome did you expect instead?
No warning
-- System Information:
Debian Release: 10.9
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable'),
(102, 'experimental'), (50, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-16-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-- Configuration Files:
/etc/logstash/jvm.options changed:
-Xms1g
-Xmx1g
-XX:CMSInitiatingOccupancyFraction=75
-XX:+UseCMSInitiatingOccupancyOnly
-Djava.awt.headless=true
-Dfile.encoding=UTF-8
-Djruby.compile.invokedynamic=true
-Djruby.jit.threshold=0
-Djruby.regexp.interruptible=true
-XX:+HeapDumpOnOutOfMemoryError
-Djava.security.egd=file:/dev/urandom
/etc/logstash/logstash.yml changed:
path.data: /var/lib/logstash
path.logs: /var/log/logstash
/etc/logstash/startup.options [Errno 13] Permission denied:
'/etc/logstash/startup.options'
################################################################################
# These settings are ONLY used by $LS_HOME/bin/system-install to create a custom
# startup script for Logstash and is not used by Logstash itself. It should
# automagically use the init system (systemd, upstart, sysv, etc.) that your
# Linux distribution uses.
#
# After changing anything here, you need to re-run $LS_HOME/bin/system-install
# as root to push the changes to the init script.
################################################################################
# Override Java location
#JAVACMD=/usr/bin/java
# Set a home directory
LS_HOME=/usr/share/logstash
# logstash settings directory, the path which contains logstash.yml
LS_SETTINGS_DIR=/etc/logstash
# Arguments to pass to logstash
LS_OPTS="--path.settings ${LS_SETTINGS_DIR}"
# Arguments to pass to java
LS_JAVA_OPTS=""
# pidfiles aren't used the same way for upstart and systemd; this is for sysv
users.
LS_PIDFILE=/var/run/logstash.pid
# user and group id to be invoked as
LS_USER=logstash
LS_GROUP=logstash
# Enable GC logging by uncommenting the appropriate lines in the GC logging
# section in jvm.options
LS_GC_LOG_FILE=/var/log/logstash/gc.log
# Open file limit
LS_OPEN_FILES=16384
# Nice level
LS_NICE=19
# Change these to have the init script named and described differently
# This is useful when running multiple instances of Logstash on the same
# physical box or vm
SERVICE_NAME="logstash"
SERVICE_DESCRIPTION="logstash"
# If you need to run a command or script before launching Logstash, put it
# between the lines beginning with `read` and `EOM`, and uncomment those lines.
###
## read -r -d '' PRESTART << EOM
## EOM
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mi, 26 mai 21, 19:06:15, Stefan Nitz wrote:
> Package: logstash
> Version: 1:6.8.16-1
> Severity: normal
Hello,
There is no such package in Debian, please report any issues to where
you obtained it from.
Kind regards,
Andrei
--
Looking after bugs assigned to unknown or inexistent packages
signature.asc
Description: PGP signature
--- End Message ---
