I2P support forum

Edit:
I am running out of ram. I increased my ram to 1GB. I still crash if my bandwidth goes over 1MB up and 1MB down.



I have been having my router crash for about 1month every few hours. I have increased the ram to 900MB but hasn't fixed it. I have more routers but this is giving me a problem for some reason.

Jun 22, 2023, 5:46 PM Crashed 62 sec ago
Jun 22, 2023, 5:32 PM Started router 2.2.1-0
Jun 22, 2023, 5:32 PM Crashed 63 sec ago
Jun 22, 2023, 4:54 PM Reachability change from IPv4: Testing; IPv6: OK to OK
Jun 22, 2023, 4:49 PM Started router 2.2.1-0
Jun 22, 2023, 4:49 PM Crashed 64 sec ago
Jun 22, 2023, 4:33 PM Reachability change from IPv4: Testing; IPv6: OK to OK
Jun 22, 2023, 4:28 PM Started router 2.2.1-0
Jun 22, 2023, 4:28 PM Crashed 63 sec ago
Jun 22, 2023, 3:31 PM Started router 2.2.1-0
Jun 22, 2023, 3:31 PM Crashed 60 sec ago
Jun 22, 2023, 2:50 PM Started router 2.2.1-0
Jun 22, 2023, 2:50 PM Crashed 63 sec ago
Jun 22, 2023, 2:23 PM Started router 2.2.1-0
Jun 22, 2023, 2:23 PM Crashed 64 sec ago
Jun 22, 2023, 1:31 PM Started router 2.2.1-0
Jun 22, 2023, 1:31 PM Crashed 61 sec ago
Jun 22, 2023, 12:42 PM Started router 2.2.1-0
Jun 22, 2023, 12:42 PM Crashed 62 sec ago
Jun 22, 2023, 11:44 AM Started router 2.2.1-0
Jun 22, 2023, 11:44 AM Crashed 60 sec ago
Jun 22, 2023, 11:27 AM Started router 2.2.1-0
Jun 22, 2023, 11:27 AM Crashed 62 sec ago
Jun 22, 2023, 11:06 AM Started router 2.2.1-0
Jun 22, 2023, 11:06 AM Crashed 63 sec ago
Jun 22, 2023, 10:56 AM Started router 2.2.1-0
Jun 22, 2023, 10:56 AM Crashed 60 sec ago
Jun 22, 2023, 10:47 AM Started router 2.2.1-0
Jun 22, 2023, 10:47 AM Crashed 63 sec ago
Jun 22, 2023, 10:26 AM Reachability change from IPv4: Testing; IPv6: OK to OK
Jun 22, 2023, 10:21 AM Started router 2.2.1-0
Jun 22, 2023, 10:21 AM Crashed 66 sec ago
Jun 22, 2023, 9:58 AM Started router 2.2.1-0
Jun 22, 2023, 9:58 AM Crashed 62 sec ago
Jun 22, 2023, 9:57 AM Started router 2.2.1-0
Jun 22, 2023, 9:57 AM Crashed 63 sec ago
Jun 22, 2023, 9:46 AM Started router 2.2.1-0
Jun 22, 2023, 9:46 AM Crashed 63 sec ago
Jun 22, 2023, 9:30 AM Started router 2.2.1-0
Jun 22, 2023, 9:30 AM Crashed 61 sec ago
Jun 22, 2023, 8:50 AM Started router 2.2.1-0
Jun 22, 2023, 8:50 AM Crashed 61 sec ago
Jun 22, 2023, 8:19 AM Started router 2.2.1-0
Jun 22, 2023, 8:19 AM Crashed 63 sec ago
Jun 22, 2023, 8:17 AM Reachability change from IPv4: Testing; IPv6: OK to OK
Jun 22, 2023, 8:12 AM Started router 2.2.1-0
Jun 22, 2023, 8:12 AM Crashed 69 sec ago
Jun 22, 2023, 8:04 AM Reachability change from IPv4: OK; IPv6: Firewalled to OK
Jun 22, 2023, 7:46 AM Started router 2.2.1-0
Jun 22, 2023, 7:46 AM Crashed 60 sec ago
Jun 22, 2023, 7:43 AM Started router 2.2.1-0
Jun 22, 2023, 7:43 AM Crashed 60 sec ago
Jun 22, 2023, 7:42 AM Reachability change from IPv4: OK; IPv6: Firewalled to OK
Jun 22, 2023, 7:26 AM Started router 2.2.1-0
Jun 22, 2023, 7:26 AM Crashed 64 sec ago
Jun 22, 2023, 6:45 AM Started router 2.2.1-0
Jun 22, 2023, 6:45 AM Crashed 63 sec ago
Jun 22, 2023, 6:39 AM Started router 2.2.1-0
Jun 22, 2023, 6:39 AM Crashed 63 sec ago
Jun 22, 2023, 6:14 AM Started router 2.2.1-0
Jun 22, 2023, 6:14 AM Crashed 62 sec ago
Jun 22, 2023, 5:50 AM Started router 2.2.1-0
Jun 22, 2023, 5:50 AM Crashed 74 sec ago
Jun 22, 2023, 4:50 AM Started router 2.2.1-0
Jun 22, 2023, 4:50 AM Crashed 70 sec ago
Jun 22, 2023, 3:13 AM Started router 2.2.1-0
Jun 22, 2023, 3:13 AM Crashed 74 sec ago
Jun 22, 2023, 2:50 AM Started router 2.2.1-0
Jun 22, 2023, 2:50 AM Crashed 61 sec ago
Jun 22, 2023, 2:33 AM Started router 2.2.1-0
Jun 22, 2023, 2:33 AM Crashed 64 sec ago
Jun 22, 2023, 1:42 AM Started router 2.2.1-0
Jun 22, 2023, 1:42 AM Crashed 63 sec ago
Jun 21, 2023, 11:30 PM Started router 2.2.1-0
Jun 21, 2023, 11:30 PM Crashed 65 sec ago


May 22, 2023, 1:29 AM Started router 2.2.1-0
May 22, 2023, 1:29 AM Crashed 3 hours ago
May 21, 2023, 9:53 PM Started router 2.2.1-0
May 21, 2023, 9:53 PM Crashed 63 sec ago
May 21, 2023, 9:52 PM Started router 2.2.1-0
May 21, 2023, 9:52 PM Crashed 62 sec ago
May 21, 2023, 9:51 PM Started router 2.2.1-0
May 21, 2023, 9:51 PM Crashed 76 sec ago
May 21, 2023, 9:49 PM Started router 2.2.1-0
May 21, 2023, 9:49 PM Crashed 73 sec ago
May 21, 2023, 9:48 PM Started router 2.2.1-0
May 21, 2023, 9:48 PM Crashed 11 min ago
May 21, 2023, 9:34 PM Started router 2.2.1-0
May 21, 2023, 9:34 PM Crashed 63 sec ago
May 21, 2023, 9:33 PM Watchdog warning
May 21, 2023, 9:32 PM Started router 2.2.1-0
May 21, 2023, 9:32 PM Crashed 61 sec ago
May 21, 2023, 9:30 PM Started router 2.2.1-0
May 21, 2023, 9:30 PM Crashed 60 sec ago
May 21, 2023, 9:27 PM Started router 2.2.1-0
May 21, 2023, 9:27 PM Crashed 64 sec ago
May 21, 2023, 9:26 PM Watchdog warning
May 21, 2023, 9:24 PM Started router 2.2.1-0



2023/06/22 08:49:36 | JVM process is gone.
2023/06/22 08:49:36 | JVM exited unexpectedly.
2023/06/22 08:49:52 | JVM process is gone.
2023/06/22 08:49:52 | Launching a JVM...
2023/06/22 08:49:52 | WrapperManager: Initializing...
2023/06/22 08:49:52 | Starting I2P 2.2.1-0
2023/06/22 08:49:52 | WARN: There may be another router already running. Waiting a while to be sure...
2023/06/22 08:50:02 | WARN: Old router was not shut down gracefully, deleting /root/.i2p/router.ping
2023/06/22 08:50:02 | INFO: No, there wasn't another router already running. Proceeding with startup.
2023/06/22 08:50:02 | INFO: Native CPUID library jcpuid-x86-linux loaded from file
2023/06/22 08:50:02 | INFO: Locally optimized library libjbigi-linux-zen_64.so loaded from file
2023/06/22 09:29:35 | JVM received a signal SIGKILL (9).
2023/06/22 09:29:35 | JVM process is gone.
2023/06/22 09:29:35 | JVM exited unexpectedly.
2023/06/22 09:29:50 | JVM process is gone.
2023/06/22 09:29:50 | Launching a JVM...
2023/06/22 09:29:50 | WrapperManager: Initializing...
2023/06/22 09:29:50 | Starting I2P 2.2.1-0
2023/06/22 09:29:50 | WARN: There may be another router already running. Waiting a while to be sure...
2023/06/22 09:30:15 | WARN: Old router was not shut down gracefully, deleting /root/.i2p/router.ping
2023/06/22 09:30:16 | INFO: No, there wasn't another router already running. Proceeding with startup.
2023/06/22 09:30:16 | INFO: Native CPUID library jcpuid-x86-linux loaded from file
2023/06/22 09:30:16 | INFO: Locally optimized library libjbigi-linux-zen_64.so loaded from file
2023/06/22 09:45:20 | JVM received a signal SIGKILL (9).
2023/06/22 09:45:20 | JVM process is gone.
2023/06/22 09:45:20 | JVM exited unexpectedly.
2023/06/22 09:45:35 | JVM process is gone.
2023/06/22 09:45:35 | Launching a JVM...
2023/06/22 09:45:35 | WrapperManager: Initializing...
2023/06/22 09:45:35 | Starting I2P 2.2.1-0
2023/06/22 09:45:35 | WARN: There may be another router already running. Waiting a while to be sure...
2023/06/22 09:46:15 | WARN: Old router was not shut down gracefully, deleting /root/.i2p/router.ping
2023/06/22 09:46:15 | INFO: No, there wasn't another router already running. Proceeding with startup.
2023/06/22 09:46:15 | INFO: Native CPUID library jcpuid-x86-linux loaded from file
2023/06/22 09:46:16 | INFO: Locally optimized library libjbigi-linux-zen_64.so loaded from file
2023/06/22 09:56:38 | JVM received a signal SIGKILL (9).
2023/06/22 09:56:38 | JVM process is gone.
2023/06/22 09:56:38 | JVM exited unexpectedly.
2023/06/22 09:56:53 | JVM process is gone.
2023/06/22 09:56:53 | Launching a JVM...
2023/06/22 09:56:53 | WrapperManager: Initializing...
2023/06/22 09:56:53 | Starting I2P 2.2.1-0
2023/06/22 09:56:53 | WARN: There may be another router already running. Waiting a while to be sure...
2023/06/22 09:57:38 | WARN: Old router was not shut down gracefully, deleting /root/.i2p/router.ping
2023/06/22 09:57:38 | INFO: No, there wasn't another router already running. Proceeding with startup.
2023/06/22 09:57:38 | INFO: Native CPUID library jcpuid-x86-linux loaded from file
2023/06/22 09:57:38 | INFO: Locally optimized library libjbigi-linux-zen_64.so loaded from file
2023/06/22 09:58:06 | JVM received a signal SIGKILL (9).
2023/06/22 09:58:06 | JVM process is gone.
2023/06/22 09:58:06 | JVM exited unexpectedly.
2023/06/22 09:58:21 | JVM process is gone.
2023/06/22 09:58:21 | Launching a JVM...
2023/06/22 09:58:21 | WrapperManager: Initializing...
2023/06/22 09:58:21 | Starting I2P 2.2.1-0
2023/06/22 09:58:21 | WARN: There may be another router already running. Waiting a while to be sure...
2023/06/22 09:58:41 | WARN: Old router was not shut down gracefully, deleting /root/.i2p/router.ping
2023/06/22 09:58:41 | INFO: No, there wasn't another router already running. Proceeding with startup.
2023/06/22 09:58:41 | INFO: Native CPUID library jcpuid-x86-linux loaded from file
2023/06/22 09:58:41 | INFO: Locally optimized library libjbigi-linux-zen_64.so loaded from file
2023/06/22 10:20:53 | JVM received a signal SIGKILL (9).
2023/06/22 10:20:53 | JVM process is gone.
2023/06/22 10:20:53 | JVM exited unexpectedly.
2023/06/22 10:21:08 | JVM process is gone.
2023/06/22 10:21:08 | Launching a JVM...
2023/06/22 10:21:08 | WrapperManager: Initializing...
2023/06/22 10:21:08 | Starting I2P 2.2.1-0
2023/06/22 10:21:08 | WARN: Old router was not shut down gracefully, deleting /root/.i2p/router.ping
2023/06/22 10:21:08 | INFO: Native CPUID library jcpuid-x86-linux loaded from file
2023/06/22 10:21:08 | INFO: Locally optimized library libjbigi-linux-zen_64.so loaded from file
2023/06/22 10:46:18 | JVM received a signal SIGKILL (9).
2023/06/22 10:46:18 | JVM process is gone.
2023/06/22 10:46:18 | JVM exited unexpectedly.
2023/06/22 10:46:33 | JVM process is gone.
2023/06/22 10:46:33 | Launching a JVM...
2023/06/22 10:46:33 | WrapperManager: Initializing...
2023/06/22 10:46:34 | Starting I2P 2.2.1-0
2023/06/22 10:46:34 | WARN: There may be another router already running. Waiting a while to be sure...
2023/06/22 10:47:14 | WARN: Old router was not shut down gracefully, deleting /root/.i2p/router.ping
2023/06/22 10:47:14 | INFO: No, there wasn't another router already running. Proceeding with startup.
2023/06/22 10:47:14 | INFO: Native CPUID library jcpuid-x86-linux loaded from file
2023/06/22 10:47:14 | INFO: Locally optimized library libjbigi-linux-zen_64.so loaded from file
2023/06/22 10:56:01 | JVM received a signal SIGKILL (9).
2023/06/22 10:56:01 | JVM process is gone.
2023/06/22 10:56:01 | JVM exited unexpectedly.
2023/06/22 10:56:17 | JVM process is gone.
2023/06/22 10:56:17 | Launching a JVM...
2023/06/22 10:56:17 | WrapperManager: Initializing...
2023/06/22 10:56:17 | Starting I2P 2.2.1-0

2023/06/22 17:32:00 | JVM process is gone.
2023/06/22 17:32:00 | JVM exited unexpectedly.
2023/06/22 17:32:15 | JVM process is gone.
2023/06/22 17:32:15 | Launching a JVM...
2023/06/22 17:32:16 | WrapperManager: Initializing...
2023/06/22 17:32:16 | Starting I2P 2.2.1-0
2023/06/22 17:32:16 | WARN: There may be another router already running. Waiting a while to be sure...
2023/06/22 17:32:31 | WARN: Old router was not shut down gracefully, deleting /root/.i2p/router.ping
2023/06/22 17:32:31 | INFO: No, there wasn't another router already running. Proceeding with startup.
2023/06/22 17:32:31 | INFO: Native CPUID library jcpuid-x86-linux loaded from file
2023/06/22 17:32:31 | INFO: Locally optimized library libjbigi-linux-zen_64.so loaded from file
2023/06/22 17:45:43 | JVM received a signal SIGKILL (9).
2023/06/22 17:45:43 | JVM process is gone.
2023/06/22 17:45:43 | JVM exited unexpectedly.
2023/06/22 17:45:58 | JVM process is gone.
2023/06/22 17:45:58 | Launching a JVM...
2023/06/22 17:45:59 | WrapperManager: Initializing...
2023/06/22 17:45:59 | Starting I2P 2.2.1-0
2023/06/22 17:45:59 | WARN: There may be another router already running. Waiting a while to be sure...
2023/06/22 17:46:24 | WARN: Old router was not shut down gracefully, deleting /root/.i2p/router.ping
2023/06/22 17:46:24 | INFO: No, there wasn't another router already running. Proceeding with startup.
2023/06/22 17:46:24 | INFO: Native CPUID library jcpuid-x86-linux loaded from file
2023/06/22 17:46:24 | INFO: Locally optimized library libjbigi-linux-zen_64.so loaded from file
2023/06/22 17:52:05 | CRIT [ShutdownHook] net.i2p.router.Router : Shutdown imminent
2023/06/22 17:52:05 | CRIT [ShutdownHook] net.i2p.router.Router : Shutdown(2) complete
2023/06/22 17:52:07 | <-- Wrapper Stopped
2023/06/22 19:04:46 | --> Wrapper Started as Daemon
2023/06/22 19:04:46 | Java Service Wrapper Community Edition 64-bit 3.5.44
2023/06/22 19:04:46 | Copyright (C) 1999-2020 Tanuki Software, Ltd. All Rights Reserved.
2023/06/22 19:04:46 | http://wrapper.tanukisoftware.com
2023/06/22 19:04:46 |
2023/06/22 19:04:46 | Launching a JVM...
2023/06/22 19:04:46 | WrapperManager: Initializing...
2023/06/22 19:04:46 | Starting I2P 2.2.1-0
2023/06/22 19:04:47 | INFO: Native CPUID library jcpuid-x86-linux loaded from file
2023/06/22 19:04:47 | INFO: Locally optimized library libjbigi-linux-zen_64.so loaded from file

A bit sparse, what does your syslog (/var/log syslog or journalctl -xb or journalctl -xb -p3) say?
My first guess would be that you're running out of memory and gets killed by some supervising instance, so have an eye on the ram consumption after starting i2p as well. sigkill is not the nicest way to end a process, but it's not a crash.
Did you find any heapdumps? If so, you might want to increase the value for -Xmx in your startscript, if i remember correctly, i2p grants 256mb by default, which is a bit on the low end if you are into i.e. excessive torrenting.

do you crash with i2p default config?
also, you can test same config with i2pd to check and debug.

I am running out of ram. I increased my ram to 1GB. I still crash if my bandwidth goes over 1MB up and 1MB down.

Pretzel1224 wrote: ↑01 Nov 2023 19:39 I am running out of ram. I increased my ram to 1GB. I still crash if my bandwidth goes over 1MB up and 1MB down.

Have same problem with i2pd?

if i2pd work fine, i think maybe some issue with JVM.

(i2pd is c++ native without jvm)