September 2025 - TOPF

studienreformforum@zapf.in post from notify@luketechnocraft.com requires approval

by studienreformforum-owner＠zapf.in

As list administrator, your authorization is requested for the following mailing list posting: List: studienreformforum(a)zapf.in From: notify(a)luketechnocraft.com Subject: Dr. Caem Ahmad The message is being held because: The message is not from a list member At your convenience, visit your dashboard to approve or deny the request.

3 Wochen, 1 Tag

1
0
0 / 0

GitLab Patch Release: 18.4.1, 18.3.3, 18.2.7

by GitLab Security Team

To view this email as a web page, go to the following address: https://page.gitlab.com/index.php/email/emailWebview?mkt_tok=MTk0LVZWQy0y... Today we are releasing versions 18.4.1, 18.3.3, 18.2.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important security fixes and we strongly recommend that all GitLab installations be upgraded to one of these versions immediately. You can see details in this patch release blog post <https://email.gitlab.com/dc/3Agyd97uNAM8boMhA7mUn5kw_aZo4gb2i4tvDHZD-xqqV...>. Please forward this alert to appropriate people at your organization and have them subscribe to Security Notices <https://email.gitlab.com/MTk0LVZWQy0yMjEAAAGdId1sd9JvvMruafgh1J9Lg9mDI-xm...>. You can also receive security blog updates by subscribing to our patch release RSS feed <https://about.gitlab.com/security-releases.xml> or our RSS feed for all GitLab releases <https://about.gitlab.com/all-releases.xml>. GitLab releases fixes for vulnerabilities in dedicated patch releases. There are two types of patch releases: scheduled releases, and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, you can visit our security FAQ <https://email.gitlab.com/MTk0LVZWQy0yMjEAAAGdId1sd8IxBll8hOt0woRhsRO5Dtea...>. You can see all of GitLab release blog posts here <https://email.gitlab.com/dc/3Agyd97uNAM8boMhA7mUn5kw_aZo4gb2i4tvDHZD-xpjV...>. Sincerely, GitLab Security Team Blog <https://email.gitlab.com/dc/3Agyd97uNAM8boMhA7mUn286MlOamUjnwRc3xx7geco=/...> Facebook <https://email.gitlab.com/MTk0LVZWQy0yMjEAAAGdId1sdzrGLWahZPrOUzyaSawAGyu1...> YouTube <https://email.gitlab.com/MTk0LVZWQy0yMjEAAAGdId1sdxXrzzOEJ5BSVwDWfmcoNnkD...> LinkedIn <https://email.gitlab.com/MTk0LVZWQy0yMjEAAAGdId1sdiuh8TpsKcWnsPXXl7BKk3zQ...> GitLab 268 Bush Street, #350, San Francisco, CA 94104, USA This email was sent to topf(a)zapf.in. You may unsubscribe <[[https://page.gitlab.com/UnsubscribePage.html?mkt_unsubscribe=1&mkt_tok=MT...]]> anytime from GitLab's marketing emails but you will still receive operational emails related to your account. Please note that security(a)gitlab.com is an unmonitored email address.

3 Wochen, 2 Tage

1
0
0 / 0

redeleitung@zapf.in post from raymondmsnow0@gmail.com requires approval

by redeleitung-owner＠zapf.in

As list administrator, your authorization is requested for the following mailing list posting: List: redeleitung(a)zapf.in From: raymondmsnow0(a)gmail.com Subject: [Plenum] [Resos] Boost Your Reach with High-Traffic Guest Posts The message is being held because: The message is not from a list member At your convenience, visit your dashboard to approve or deny the request.

1 Monat

1
0
0 / 0

ZFS resilver_finish event for rpool on proxmox

by root

ZFS has finished a resilver: eid: 13 class: resilver_finish host: proxmox time: 2025-09-15 21:35:07+0200 pool: rpool state: DEGRADED scan: resilvered 910G in 00:11:34 with 0 errors on Mon Sep 15 21:35:07 2025 config: NAME STATE READ WRITE CKSUM rpool DEGRADED 0 0 0 mirror-0 DEGRADED 0 0 0 nvme1n1p3 ONLINE 0 0 0 replacing-1 DEGRADED 0 0 0 nvme0n1p3/old REMOVED 0 0 0 nvme0n1p3 ONLINE 0 0 0 errors: No known data errors

1 Monat

1
0
0 / 0

Re: [Ticket#2025091503031399] Server - Disk Failure - AX52 #2405763 (116.202.37.55, 2a01:4f8:231:2e04::/64)

by Support - Hetzner Online GmbH

Sehr geehrte Damen und Herren, wie gewünscht, haben wir den defekten Datenträger ersetzt und den Server wieder ins installierte System gebootet. Mit freundlichen Grüßen / Kind regards Marcel Groß Please help us to improve our processes (~10sec): https://feedback.hetzner.com/?id=eiIKzX&i=2025091503031399 Hetzner Online GmbH 08223 Falkenstein / Germany Tel: +49 3745 744 47 100 Fax: +49 3745 744 47 1050 www.hetzner.com Register Court: Registergericht Ansbach, HRB 6089 CEO: Martin Hetzner, Stephan Konvickova, Günther Müller For the purposes of this communication, we may save some of your personal data. For information on our data privacy policy, please see: https://www.hetzner.com/de/privacy-policy-notice 15.09.2025 20:57 - topf(a)zapf.in schrieb: > > > ######################################## > > No preferred date! > Defective drive(s): unknown > Functional drive(s): S676NU0W575753 > > ######################################## > > SSD defekt, bitte tauschen > > SMART log: > root@proxmox:~# smartctl -a /dev/nvme0 > smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.8.4-2-pve] (local build) > Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org > > Smartctl open device: /dev/nvme0 failed: Resource temporarily unavailable > root@proxmox:~# zpool status > pool: rpool > state: DEGRADED > status: One or more devices has been removed by the administrator. > Sufficient replicas exist for the pool to continue functioning in a > degraded state. > action: Online the device using zpool online' or replace the device with > 'zpool replace'. > scan: scrub repaired 0B in 00:14:17 with 0 errors on Sun Aug 10 00:38:18 2025 > config: > > NAME STATE READ WRITE CKSUM > rpool DEGRADED 0 0 0 > mirror-0 DEGRADED 0 0 0 > nvme1n1p3 ONLINE 0 0 0 > nvme0n1p3 REMOVED 0 0 0 > > errors: No known data errors > > [10244621.755406] nvme nvme0: I/O tag 202 (80ca) opcode 0x1 (I/O Cmd) QID 3 > timeout, aborting req_op:WRITE(1) size:110592 > [10244621.755691] nvme nvme0: I/O tag 807 (7327) opcode 0x1 (I/O Cmd) QID 12 > timeout, aborting req_op:WRITE(1) size:131072 > [10244621.948406] nvme nvme0: I/O tag 236 (d0ec) opcode 0x1 (I/O Cmd) QID 5 > timeout, aborting req_op:WRITE(1) size:4096 > [10244624.064646] nvme nvme0: I/O tag 808 (f328) opcode 0x1 (I/O Cmd) QID 12 > timeout, aborting req_op:WRITE(1) size:90112 > [10244624.641398] nvme nvme0: I/O tag 203 (20cb) opcode 0x1 (I/O Cmd) QID 3 > timeout, aborting req_op:WRITE(1) size:4096 > [10244624.641695] nvme nvme0: I/O tag 186 (30ba) opcode 0x1 (I/O Cmd) QID 14 > timeout, aborting req_op:WRITE(1) size:4096 > [10244631.490374] nvme nvme0: I/O tag 237 (b0ed) opcode 0x2 (I/O Cmd) QID 5 > timeout, aborting req_op:READ(0) size:12288 > [10244631.490667] nvme nvme0: I/O tag 238 (c0ee) opcode 0x2 (I/O Cmd) QID 5 > timeout, aborting req_op:READ(0) size:12288 > [10244651.964310] nvme nvme0: I/O tag 202 (80ca) opcode 0x1 (I/O Cmd) QID 3 > timeout, reset controller > [10244720.055098] INFO: task txg_sync:545 blocked for more than 122 seconds. > [10244720.055346] Tainted: P O 6.8.4-2-pve #1 > [10244720.055537] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this > message. > [10244720.055722] task:txg_sync state:D stack:0 pid:545 tgid:545 > ppid:2 flags:0x00004000 > [10244720.055912] Call Trace: > [10244720.056104] <TASK> > [10244720.056288] __schedule+0x401/0x15e0 > [10244720.056475] ? ttwu_queue_wakelist+0x101/0x110 > [10244720.056660] ? srso_alias_return_thunk+0x5/0xfbef5 > [10244720.056846] ? try_to_wake_up+0x248/0x5f0 > [10244720.057033] schedule+0x33/0x110 > [10244720.057222] cv_wait_common+0x109/0x140 [spl] > [10244720.057405] ? __pfx_autoremove_wake_function+0x10/0x10 > [10244720.057587] __cv_wait+0x15/0x30 [spl] > [10244720.057770] zil_sync+0xdd/0x580 [zfs] > [10244720.058034] ? spa_taskq_dispatch_ent+0x66/0xe0 [zfs] > [10244720.058295] ? srso_alias_return_thunk+0x5/0xfbef5 > [10244720.058477] ? zio_issue_async+0x53/0xb0 [zfs] > [10244720.058724] ? srso_alias_return_thunk+0x5/0xfbef5 > [10244720.058904] ? zio_nowait+0xd2/0x1c0 [zfs] > [10244720.059154] dmu_objset_sync+0x441/0x600 [zfs] > [10244720.059408] dsl_dataset_sync+0x61/0x200 [zfs] > [10244720.059655] dsl_pool_sync+0xb2/0x4e0 [zfs] > [10244720.059902] spa_sync+0x578/0x1030 [zfs] > [10244720.060163] ? srso_alias_return_thunk+0x5/0xfbef5 > [10244720.060344] ? srso_alias_return_thunk+0x5/0xfbef5 > [10244720.060520] ? spa_txg_history_init_io+0x120/0x130 [zfs] > [10244720.060761] txg_sync_thread+0x1fd/0x390 [zfs] > [10244720.060996] ? __pfx_txg_sync_thread+0x10/0x10 [zfs] > [10244720.061222] ? __pfx_thread_generic_wrapper+0x10/0x10 [spl] > [10244720.061387] thread_generic_wrapper+0x5c/0x70 [spl] > [10244720.061549] kthread+0xef/0x120 > [10244720.061702] ? __pfx_kthread+0x10/0x10 > [10244720.061849] ret_from_fork+0x44/0x70 > [10244720.061996] ? __pfx_kthread+0x10/0x10 > [10244720.062145] ret_from_fork_asm+0x1b/0x30 > [10244720.062294] </TASK> > [10244720.062454] INFO: task zvol:556428 blocked for more than 122 seconds. > [10244720.062602] Tainted: P O 6.8.4-2-pve #1 > [10244720.062745] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this > message. > [10244720.062891] task:zvol state:D stack:0 pid:556428 tgid:556428 > ppid:2 flags:0x00004000 > [10244720.063044] Call Trace: > [10244720.063189] <TASK> > [10244720.063330] __schedule+0x401/0x15e0 > [10244720.063471] ? zio_add_child+0x13d/0x160 [zfs] > [10244720.063679] ? srso_alias_return_thunk+0x5/0xfbef5 > [10244720.063821] ? srso_alias_return_thunk+0x5/0xfbef5 > [10244720.06396...

1 Monat

1
0
0 / 0

[Ticket#2025091503031399] RE: Server - Disk Failure - AX52 #2405763 (116.202.37.55, 2a01:4f8:231:2e04::/64)

by Info - Hetzner Online GmbH

[english version below] Guten Tag, Ihre Nachricht ist bei uns eingetroffen. Schön, dass Sie uns kontaktieren. Sie ahnen es vielleicht schon: Sie lesen gerade eine automatisch verschickte E-Mail. In Kürze bekommen Sie noch eine ganz persönliche Antwort von uns. Geben Sie uns ein wenig Zeit, um diese zu schreiben. Vielen Dank! Mit freundlichen Grüßen Ihr Hetzner Online Team Hetzner Online GmbH Industriestr. 25 91710 Gunzenhausen Tel.: +49 9831 505-0 Fax: +49 9831 505-3 www.hetzner.com Registergericht Ansbach, HRB 6089 Geschäftsführer: Martin Hetzner, Stephan Konvickova, Günther Müller Hinweise zur Verarbeitung Ihrer personenbezogenen Daten im Rahmen der Kommunikation mit Ihnen finden Sie unter: www.hetzner.com/de/privacy-policy-notice --------------------------------------------------------------------- Hi there We received your email. Thanks for writing to us. You have probably realized by now that this is an automated message. We need some time to process each email that we receive, but we will write back to you personally as soon as we can. Thank you for your understanding! Kind regards Your Hetzner Online Team Hetzner Online GmbH Industriestr. 25 91710 Gunzenhausen / Germany Tel.: +49 9831 505-0 Fax: +49 9831 505-3 www.hetzner.com Register Court: Registergericht Ansbach, HRB 6089 CEO: Martin Hetzner, Stephan Konvickova, Günther Müller For the purposes of this communication, we may save some of your personal data. For information on our data privacy policy, please see: www.hetzner.com/privacy-policy-notice part of the request: > > > ######################################## > > No preferred date! > Defective drive(s): unknown > Functional drive(s): S676NU0W575753 > > ######################################## > > SSD defekt, bitte tauschen > > SMART log: > root@proxmox:~# smartctl -a /dev/nvme0 > smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.8.4-2-pve] (local build) > Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org > > Smartctl open device: /dev/nvme0 failed: Resource temporarily unavailable > root@proxmox:~# zpool status > pool: rpool > state: DEGRADED > status: One or more devices has been removed by the administrator. > Sufficient replicas exist for the pool to continue functioning in a > degraded state. > action: Online the device using zpool online' or replace the device with > 'zpool replace'. > scan: scrub repaired 0B in 00:14:17 with 0 errors on Sun Aug 10 00:38:18 2025 > config: > > NAME STATE READ WRITE CKSUM > rpool DEGRADED 0 0 0 > mirror-0 DEGRADED 0 0 0 > nvme1n1p3 ONLINE 0 0 0 > nvme0n1p3 REMOVED 0 0 0 > > errors: No known data errors > > [10244621.755406] nvme nvme0: I/O tag 202 (80ca) opcode 0x1 (I/O Cmd) QID 3 timeout, > aborting req_op:WRITE(1) size:110592 > [10244621.755691] nvme nvme0: I/O tag 807 (7327) opcode 0x1 (I/O Cmd) QID 12 timeout, > aborting req_op:WRITE(1) size:131072 > [10244621.948406] nvme nvme0: I/O tag 236 (d0ec) opcode 0x1 (I/O Cmd) QID 5 timeout, > aborting req_op:WRITE(1) size:4096 > [10244624.064646] nvme nvme0: I/O tag 808 (f328) opcode 0x1 (I/O Cmd) QID 12 timeout, > aborting req_op:WRITE(1) size:90112 > [10244624.641398] nvme nvme0: I/O tag 203 (20cb) opcode 0x1 (I/O Cmd) QID 3 timeout, > aborting req_op:WRITE(1) size:4096 > [10244624.641695] nvme nvme0: I/O tag 186 (30ba) opcode 0x1 (I/O Cmd) QID 14 timeout, > aborting req_op:WRITE(1) size:4096 > [10244631.490374] nvme nvme0: I/O tag 237 (b0ed) opcode 0x2 (I/O Cmd) QID 5 timeout, ...

1 Monat

1
0
0 / 0

GitLab Patch Release: 18.3.2, 18.2.6, 18.1.6

by GitLab Security Team

To view this email as a web page, go to the following address: https://page.gitlab.com/index.php/email/emailWebview?mkt_tok=MTk0LVZWQy0y... Today we are releasing versions 18.3.2, 18.2.6, 18.1.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important security fixes and we strongly recommend that all GitLab installations be upgraded to one of these versions immediately. You can see details in this patch release blog post <https://email.gitlab.com/dc/3Agyd97uNAM8boMhA7mUn5kw_aZo4gb2i4tvDHZD-xqjT...>. Please forward this alert to appropriate people at your organization and have them subscribe to Security Notices <https://email.gitlab.com/MTk0LVZWQy0yMjEAAAGc1Gd5I-9DMFfpqXN_VAPuSxCCjGus...>. You can also receive security blog updates by subscribing to our patch release RSS feed <https://about.gitlab.com/security-releases.xml> or our RSS feed for all GitLab releases <https://about.gitlab.com/all-releases.xml>. GitLab releases fixes for vulnerabilities in dedicated patch releases. There are two types of patch releases: scheduled releases, and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, you can visit our security FAQ <https://email.gitlab.com/MTk0LVZWQy0yMjEAAAGc1Gd5I_OFc05uwK2whrh-JcR6NwYj...>. You can see all of GitLab release blog posts here <https://email.gitlab.com/dc/3Agyd97uNAM8boMhA7mUn5kw_aZo4gb2i4tvDHZD-xpjV...>. Sincerely, GitLab Security Team Blog <https://email.gitlab.com/dc/3Agyd97uNAM8boMhA7mUn286MlOamUjnwRc3xx7geco=/...> Facebook <https://email.gitlab.com/MTk0LVZWQy0yMjEAAAGc1Gd5JIDwfU0T06TjGRY5w1_cBxGq...> YouTube <https://email.gitlab.com/MTk0LVZWQy0yMjEAAAGc1Gd5I3NUy2l9UIxLXDenpvar_rqn...> LinkedIn <https://email.gitlab.com/MTk0LVZWQy0yMjEAAAGc1Gd5I7wV-SuzO_2VEd3kRqCBEw_-...> GitLab 268 Bush Street, #350, San Francisco, CA 94104, USA This email was sent to topf(a)zapf.in. You may unsubscribe <[[https://page.gitlab.com/UnsubscribePage.html?mkt_unsubscribe=1&mkt_tok=MT...]]> anytime from GitLab's marketing emails but you will still receive operational emails related to your account. Please note that security(a)gitlab.com is an unmonitored email address.

1 Monat, 1 Woche

1
0
0 / 0

studienreformforum@zapf.in post from notify@nexonmailbox.com requires approval

by studienreformforum-owner＠zapf.in

As list administrator, your authorization is requested for the following mailing list posting: List: studienreformforum(a)zapf.in From: notify(a)nexonmailbox.com Subject: Dr. Kukresh The message is being held because: The message is not from a list member At your convenience, visit your dashboard to approve or deny the request.

1 Monat, 2 Wochen

1
0
0 / 0

ZFS device fault for pool rpool on proxmox

by root

ZFS has detected that a device was removed. impact: Fault tolerance of the pool may be compromised. eid: 50 class: statechange state: REMOVED host: proxmox time: 2025-09-02 05:07:32+0200 vpath: /dev/nvme0n1p3 vguid: 0x7459C86D6E3C468B pool: rpool (0x9013CD2701DD5509)

1 Monat, 2 Wochen

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

TOPF September 2025