Closed kaneruan closed 3 years ago
any one help?
We're missing some repro steps after docker-compose up -d
. You tried to send events to your Sentry install and they're not showing up? How did you try to send the events?
I am seeing some network connectivity issues in the logfile you shared, but without more info on the steps you're following I'm not sure what matters and what's a red herring.
It simply looks like your server is quite overloaded and keeps processing through a backlog. I advice you to leave it running for a while and try to minimize any new events coming in to see whether it stabilizes.
I have the same issue. My kafka & zookeeper services keep restarting.
Kafka logs (this endlessly repeats):
===> User uid=1000(appuser) gid=1000(appuser) groups=1000(appuser) ===> Configuring ... ===> Running preflight checks ... ===> Check if /var/lib/kafka/data is writable ... ===> Check if Zookeeper is healthy ... SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/usr/share/java/cp-base-new/slf4j-log4j12-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/usr/share/java/cp-base-new/slf4j-simple-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory] log4j:WARN No appenders could be found for logger (io.confluent.admin.utils.cli.ZookeeperReadyCommand). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Zookeeper logs (also endlessly repeats):
===> User uid=1000(appuser) gid=1000(appuser) groups=1000(appuser) ===> Configuring ... ===> Running preflight checks ... ===> Check if /var/lib/zookeeper/data is writable ... Command [/usr/local/bin/dub path /var/lib/zookeeper/data writable] FAILED !
This all started happening after pulling in the latest repo changes (coming from commit 0cfaa73b0586018c667b0c8cafa2c605a7bf29f5) and running the install script again as usual (have done this many times).
Pretty sure you ran out of space @djbe
Pretty sure you ran out of space @djbe
Hmmm no, disk use is at 45%
@djbe then I think your issue might be related to #1009. Can you try my suggestion there?
Can confirm that your suggestion there fixes this issue 🎉
Looks like the Kafka upgrade was not smooth. I'll dig into this.
Folding this into #1009 as they seem to be the same and #1009 is a clearer report.
Version Information
Version: 21.6.1
Steps to Reproduce
./install.sh docker-compose up -d
Expected Result
Actual Result
Logs