Januar 2025 - TOPF - ZaPF-Lists

by MAILER-DAEMON＠zapf.in

This is the mail system at host mail.zapf.in. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <bksellers3(a)gmail.com>: host gmail-smtp-in.l.google.com[108.177.127.26] said: 550-5.2.1 The user you are trying to contact is receiving mail at a rate that 550-5.2.1 prevents additional messages from being delivered. For more 550-5.2.1 information, go to 550 5.2.1 https://support.google.com/mail/?p=ReceivingRatePerm a640c23a62f3a-ab2c95cf1c2si186818166b.671 - gsmtp (in reply to RCPT TO command)

9 Monate, 1 Woche

1
0
0 / 0

ZFS scrub_finish event for rpool on proxmox

by root

ZFS has finished a scrub: eid: 19 class: scrub_finish host: proxmox time: 2025-01-09 20:04:41+0100 pool: rpool state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-9P scan: scrub repaired 0B in 00:09:52 with 0 errors on Thu Jan 9 20:04:41 2025 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 nvme1n1p3 ONLINE 0 0 0 nvme0n1p3 ONLINE 0 0 2 errors: No known data errors

9 Monate, 1 Woche

1
0
0 / 0

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

by Support - Hetzner Online GmbH

Dear Client we now checked this and couldn't find any issues with the drives. ------------------------------------------------- Hardware Check report for IP 116.202.37.55 Disk check: OK NVMe SSD `S676NU0W627099`: OK S.M.A.R.T Tests: OK Error counters: OK NVMe SSD `S676NU0W575753`: OK S.M.A.R.T Tests: OK Error counters: OK ------------------------------------------------- /dev/nvme0n1 1.02 TB S676NU0W627099 GXA7801Q 27°C 1838 hours PCIe Gen active: Gen4 drive_writes_per_day 0 critical_warning 0 available_spare 100% available_spare_threshold 10% percentage_used 6% media_errors 0 num_err_log_entries 0 --------------------------------------- /dev/nvme1n1 1.02 TB S676NU0W575753 GXA7801Q 33°C 1676 hours PCIe Gen active: Gen4 drive_writes_per_day 0 critical_warning 0 available_spare 100% available_spare_threshold 10% percentage_used 5% media_errors 0 num_err_log_entries 0 --------------------------------------- We now booted the server back to the installed system. Mit freundlichen Grüßen / Kind regards Marcel Groß 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 09.01.2025 18:19 - topf(a)zapf.in schrieb: > > > ######################################## > > No preferred date! > Defective drive(s): unknown > Functional drive(s): S676NU0W575753 > > ######################################## > > Leider ist die von Ihnen vor kurzem getauschte Ersatz-SSD innerhalb von kurzer > Zeit ebenfalls defekt gewesen. > > SMART log: > root@proxmox:~# zpool status > pool: rpool > state: DEGRADED > status: One or more devices are faulted in response to persistent errors. > Sufficient replicas exist for the pool to continue functioning in a > degraded state. > action: Replace the faulted device, or use 'zpool clear' to mark the device > repaired. > scan: resilvered 718G in 00:09:09 with 0 errors on Tue Dec 24 00:13:45 2024 > config: > > NAME STATE READ WRITE CKSUM > rpool DEGRADED 0 0 0 > mirror-0 DEGRADED 0 0 0 > nvme1n1p3 ONLINE 0 0 0 > nvme0n1p3 FAULTED 6 1.11K 0 too many errors > > errors: No known data errors > > root@proxmox:~# smartctl -a /dev/nvme0n1 > 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 > > Read NVMe Identify Controller failed: NVME_IOCTL_ADMIN_CMD: Input/output error >

9 Monate, 1 Woche

1
0
0 / 0

ZFS resilver_finish event for rpool on proxmox

by root

ZFS has finished a resilver: eid: 15 class: resilver_finish host: proxmox time: 2025-01-09 19:49:47+0100 pool: rpool state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-9P scan: resilvered 29.5G in 00:00:34 with 0 errors on Thu Jan 9 19:49:47 2025 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 nvme1n1p3 ONLINE 0 0 0 nvme0n1p3 ONLINE 0 0 2 errors: No known data errors

9 Monate, 1 Woche

1
0
0 / 0

[Ticket#2025010903027241] 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 > > ######################################## > > Leider ist die von Ihnen vor kurzem getauschte Ersatz-SSD innerhalb von kurzer Zeit > ebenfalls defekt gewesen. > > SMART log: > root@proxmox:~# zpool status > pool: rpool > state: DEGRADED > status: One or more devices are faulted in response to persistent errors. > Sufficient replicas exist for the pool to continue functioning in a > degraded state. > action: Replace the faulted device, or use 'zpool clear' to mark the device > repaired. > scan: resilvered 718G in 00:09:09 with 0 errors on Tue Dec 24 00:13:45 2024 > config: > > NAME STATE READ WRITE CKSUM > rpool DEGRADED 0 0 0 > mirror-0 DEGRADED 0 0 0 > nvme1n1p3 ONLINE 0 0 0 > nvme0n1p3 FAULTED 6 1.11K 0 too many errors > > errors: No known data errors > > root@proxmox:~# smartctl -a /dev/nvme0n1 > 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 > > Read NVMe Identify Controller failed: NVME_IOCTL_ADMIN_CMD: Input/output error ...

9 Monate, 1 Woche

1
0
0 / 0

Undelivered Mail Returned to Sender

by MAILER-DAEMON＠zapf.in

This is the mail system at host mail.zapf.in. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <nannonr(a)gmail.com>: host gmail-smtp-in.l.google.com[74.125.128.27] said: 550-5.2.1 The user you are trying to contact is receiving mail at a rate that 550-5.2.1 prevents additional messages from being delivered. For more 550-5.2.1 information, go to 550 5.2.1 https://support.google.com/mail/?p=ReceivingRatePerm a640c23a62f3a-ab2c9411cf1si876866b.276 - gsmtp (in reply to RCPT TO command)

9 Monate, 1 Woche

1
0
0 / 0

Let's Encrypt certificate expiration notice for domain "wiki.test.zapf.in"

by Let's Encrypt Expiry Bot

Hello, Your certificate (or certificates) for the names listed below will expire in 19 days (on 2025-01-28). Please make sure to renew your certificate before then, or visitors to your web site will encounter errors. We recommend renewing certificates automatically when they have a third of their total lifetime left. For Let's Encrypt's current 90-day certificates, that means renewing 30 days before expiration. See https://letsencrypt.org/docs/integration-guide/ for details. wiki.test.zapf.in For details about when we send these emails, please visit: https://letsencrypt.org/docs/expiration-emails/ In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message. For any questions or support, please visit: https://community.letsencrypt.org/ Unfortunately, we can't provide support by email. To learn more about the latest technical and organizational updates from Let's Encrypt, sign up for our newsletter: https://letsencrypt.org/opt-in/ If you are receiving this email in error, unsubscribe at: http://delivery.letsencrypt.org/track/unsub.php?u=30850198&id=e7dec6e590b... Please note that this would also unsubscribe you from other Let's Encrypt service notices, including expiration reminders for any other certificates. Regards, The Let's Encrypt Team

9 Monate, 1 Woche

1
0
0 / 0

GitLab Patch Release: 17.7.1, 17.6.3, 17.5.5

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 17.7.1, 17.6.3, 17.5.5 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important security fixes and <strong>we strongly recommend that all GitLab installations be upgraded to one of these versions immediately</strong>. You can see details in this patch release blog post <https://about.gitlab.com/releases/2025/01/08/patch-release-gitlab-17-7-1-...>. Please forward this alert to appropriate people at your organization and have them subscribe to Security Notices <https://about.gitlab.com/company/contact/>. 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://about.gitlab.com/security/faq/>. You can see all of GitLab release blog posts here <https://about.gitlab.com/releases/categories/releases/>. Sincerely, GitLab Security Team 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.

9 Monate, 1 Woche

1
0
0 / 0

Undelivered Mail Returned to Sender

by MAILER-DAEMON＠zapf.in

This is the mail system at host mail.zapf.in. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <bneuroth3(a)gmail.com>: host gmail-smtp-in.l.google.com[142.251.18.26] said: 550-5.2.1 The user you are trying to contact is receiving mail at a rate that 550-5.2.1 prevents additional messages from being delivered. For more 550-5.2.1 information, go to 550 5.2.1 https://support.google.com/mail/?p=ReceivingRatePerm a640c23a62f3a-aac0f0c8e05si2444061366b.834 - gsmtp (in reply to RCPT TO command)

9 Monate, 1 Woche

1
0
0 / 0

Let's Encrypt certificate expiration notice for domain "engel.zapf.in"

by Let's Encrypt Expiry Bot

Hello, Your certificate (or certificates) for the names listed below will expire in 6 days (on 2025-01-15). Please make sure to renew your certificate before then, or visitors to your web site will encounter errors. We recommend renewing certificates automatically when they have a third of their total lifetime left. For Let's Encrypt's current 90-day certificates, that means renewing 30 days before expiration. See https://letsencrypt.org/docs/integration-guide/ for details. engel.zapf.in For details about when we send these emails, please visit: https://letsencrypt.org/docs/expiration-emails/ In particular, note that this reminder email is still sent if you've obtained a slightly different certificate by adding or removing names. If you've replaced this certificate with a newer one that covers more or fewer names than the list above, you may be able to ignore this message. For any questions or support, please visit: https://community.letsencrypt.org/ Unfortunately, we can't provide support by email. To learn more about the latest technical and organizational updates from Let's Encrypt, sign up for our newsletter: https://letsencrypt.org/opt-in/ If you are receiving this email in error, unsubscribe at: http://delivery.letsencrypt.org/track/unsub.php?u=30850198&id=3e742a01a06... Please note that this would also unsubscribe you from other Let's Encrypt service notices, including expiration reminders for any other certificates. Regards, The Let's Encrypt Team

9 Monate, 1 Woche

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

TOPF Januar 2025