From: Timo Eissler <timo@teissler.de>
To: development@lists.ipfire.org
Subject: Re: mirror
Date: Wed, 05 Aug 2015 11:01:19 +0200 [thread overview]
Message-ID: <55C1D0DF.3050204@teissler.de> (raw)
In-Reply-To: <55C0FEBA.30908@dailydata.net>
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
Hello Rod,
the correct place to ask for this would be the IPFire Mirror Mailinglist.
http://lists.ipfire.org/mailman/listinfo/ipfire-mirrors
I don't know what the problem was, but as i started to investigate the
issue your mirror check service recovers.
Maybe someone else from the ipfire admins did something, but
nevertheless your mirror is in OK state now.
If this issue occur's again please write to the mirror mailinglist.
Thank you and kind regards,
Timo
Am 04.08.2015 um 20:04 schrieb Rod Rodolico:
> this is likely not the correct place to ask this, but I'm not sure where
> to do it. I mirror IPFire, and have been getting the following warnings
> repeatedly over the past couple of weeks. I have verified the timestamp
> on my server is correct. Is it possible the primary mirror has a
> date/time issue?
>
> ***** Icinga *****
>
> Notification Type: PROBLEM
>
> Service: MirrorSync
> Host: IPFire Mirror mirror.smartappliances.us
> Address: 74.124.0.218
> State: WARNING
>
> Date/Time: Tue Aug 4 18:26:03 CEST 2015
>
> Additional Info:
>
> WARNING: http://mirror.smartappliances.us/ipfire/ is more than 12h off:
> 2d 16h 52m 44s
>
--
Timo Eissler
Senior Project Engineer / Consultant
Am Zuckerberg 54
D-71640 Ludwigsburg
Tel.: +49 7141 4094003
Mobil.: +49 151 20650311
Email: timo(a)teissler.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-05 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 18:04 mirror Rod Rodolico
2015-08-05 9:01 ` Timo Eissler [this message]
2015-08-05 10:07 ` mirror Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55C1D0DF.3050204@teissler.de \
--to=timo@teissler.de \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox