Open Slyke opened 1 month ago
I'm also getting an error updating from 1.14.3 to 1.15.0 (or straigh to 1.15.1) database, core, jobservice, redis and registry in crashloopbackoff
database
database upgrade DB from 14 to 15
database popen failure: Cannot allocate memory
database initdb: error: program "postgres" is needed by initdb but was not found in the same directory as "/usr/pgsql/15/bin/initdb"
core
goroutine 1 gp=0xc0000061c0 m=0 mp=0x4418680 [running]:
runtime.systemstack_switch()
/usr/local/go/src/runtime/asm_amd64.s:474 +0x8 fp=0xc00013e750 sp=0xc00013e740 pc=0x474a08
runtime.main()
/usr/local/go/src/runtime/proc.go:171 +0x67 fp=0xc00013e7e0 sp=0xc00013e750 pc=0x442467
runtime.goexit({})
/usr/local/go/src/runtime/asm_amd64.s:1695 +0x1 fp=0xc00013e7e8 sp=0xc00013e7e0 pc=0x476a21
rax 0x0
rbx 0x1
rcx 0x7f9186eb2dbc
rdx 0x6
rdi 0x1
rsi 0x1
rbp 0x7f9186e25740
rsp 0x7fffe32d0950
r8 0x0
r9 0x73
r10 0x8
r11 0x246
r12 0x6
r13 0x0
r14 0x4417840
r15 0x1ffffffffffffff
rip 0x7f9186eb2dbc
rflags 0x246
cs 0x33
fs 0x0
gs 0x0
jobserver also like the core pod, runtime errors on same asm_amd64
redis
1:C 30 Aug 2024 03:52:13.902 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 30 Aug 2024 03:52:13.902 * Redis version=7.2.4, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 30 Aug 2024 03:52:13.902 * Configuration loaded
1:M 30 Aug 2024 03:52:13.903 * monotonic clock: POSIX clock_gettime
1:M 30 Aug 2024 03:52:13.903 # Failed to write PID file: Permission denied
_._
_.-``__ ''-._
_.-`` `. `_. ''-._ Redis 7.2.4 (00000000/0) 64 bit
.-`` .-```. ```\/ _.,_ ''-._
( ' , .-` | `, ) Running in standalone mode
|`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
| `-._ `._ / _.-' | PID: 1
`-._ `-._ `-./ _.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' | https://redis.io
`-._ `-._`-.__.-'_.-' _.-'
|`-._`-._ `-.__.-' _.-'_.-'|
| `-._`-._ _.-'_.-' |
`-._ `-._`-.__.-'_.-' _.-'
`-._ `-.__.-' _.-'
`-._ _.-'
`-.__.-'
1:M 30 Aug 2024 03:52:13.903 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:M 30 Aug 2024 03:52:13.903 # Fatal: Can't initialize Background Jobs. Error message: Operation not permitted
registry even start for a while, then goes on the same error as core and jobservice
registry 10.20.91.16 - - [30/Aug/2024:03:55:52 +0000] "GET / HTTP/1.1" 200 0 "" "kube-probe/1.26"
registry 10.20.91.16 - - [30/Aug/2024:03:56:02 +0000] "GET / HTTP/1.1" 200 0 "" "kube-probe/1.26"
registry 10.20.91.16 - - [30/Aug/2024:03:56:02 +0000] "GET / HTTP/1.1" 200 0 "" "kube-probe/1.26"
registry 10.20.91.16 - - [30/Aug/2024:03:56:12 +0000] "GET / HTTP/1.1" 200 0 "" "kube-probe/1.26"
registryctl goroutine 1 gp=0xc0000061c0 m=0 mp=0x1f3ebc0 [running]:
registryctl runtime.systemstack_switch()
registryctl /usr/local/go/src/runtime/asm_amd64.s:474 +0x8 fp=0xc00011a750 sp=0xc00011a740 pc=0x472888
registryctl runtime.main()
registryctl /usr/local/go/src/runtime/proc.go:171 +0x67 fp=0xc00011a7e0 sp=0xc00011a750 pc=0x441427
registryctl runtime.goexit({})
registryctl /usr/local/go/src/runtime/asm_amd64.s:1695 +0x1 fp=0xc00011a7e8 sp=0xc00011a7e0 pc=0x4748a1
registryctl
registryctl rax 0x0
registryctl rbx 0x1
registryctl rcx 0x7ff5d1eb6dbc
registryctl rdx 0x6
registryctl rdi 0x1
registryctl rsi 0x1
registryctl rbp 0x7ff5d1e29740
registryctl rsp 0x7ffc7da59ac0
registryctl r8 0x0
registryctl r9 0x73
registryctl r10 0x8
registryctl r11 0x246
registryctl r12 0x6
registryctl r13 0x0
registryctl r14 0x1f3e180
registryctl r15 0x1ffffffffffffff
registryctl rip 0x7ff5d1eb6dbc
registryctl rflags 0x246
registryctl cs 0x33
registryctl fs 0x0
registryctl gs 0x0
anyhow its now impossible to upgrade from version 1.14.3 to whatever new 1.15 version (I'm using rancher btw)
How do you upgrade your helm harbor? I cannot reproduce this issue at my side. May need more contexts here. e.g. any configurations apply to your database settings?
Helm version:
Harbor version:
Logs:
Pod description: