From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: "Alexander Strasser" <eclipse7@gmx.net>, "Nikolay Aleksandrov" <razor@blackwall.org>, "Reimar Döffinger" <Reimar.Doeffinger@gmx.de> Subject: Re: [FFmpeg-devel] ffmpeg.org issue today Date: Sun, 7 Aug 2022 11:33:56 +0200 Message-ID: <20220807093356.GO2088045@pb2> (raw) In-Reply-To: <20220727111645.GX2088045@pb2> [-- Attachment #1.1: Type: text/plain, Size: 3528 bytes --] Hi everyone as some may have noticed there was a 2nd hang happening yesterday 5th/6th august so heres a update about what i/we know/guess the 2nd hang seems to have looked like the first. ive spend some time yesterday looking over logs, there are some showers of slightly odd entries in the apache webserver logs, similar entries occured 3 times, 2 of which preceeded the server hangs by 1-2 minutes these entries come from 2 IP addresses 143.198.181.190 and 159.89.231.156 first preceeded the first hang and 2nd the 2nd hang https://www.malwareurl.com/listing.php?domain=143.198.181.190 says "Vulnerability Scanner" https://www.malwareurl.com/listing.php?domain=159.89.231.156 says "Brute-force attacker IP" it seemed these IPs spidered over random bits of the webpage, lots of gitweb a little bit of old trac links and other tiny bits of random bits, some nonsensical urls too with randomly faked browser ids all of this is alot of guessing but if we assume this was some sort of Vulnerability scanner seaching for some interresting bits on public web (where it maybe did not find much) a subsequent step of the scanner may have triggered a unfixed bug in something that caused the server to hang. thats alot speculation, and other things are possible including some hw issue that got triggered from higher load no signs of any successfull intrusion, not even anything crashing, its just the whole box hanging raz has updated the kernel now beyond what is teh default for our ubuntu also i recommand everyone to always check signatures of releases that obviosuly is not just for ffmpeg but for anything you download from the internet. thx On Wed, Jul 27, 2022 at 01:16:45PM +0200, Michael Niedermayer wrote: > Hi all > > ffmpeg.org was down today, heres what I know & what happened > > i woke up, looked at IRC saw someone saying ffmpeg.org is down, tried loging > in with ssh and that timed out (i kept trying to login while trying other things) > i mailed the other root admins and started to look around > what i found was the host and VM where running, no signs of any anomalies on the host > loging into the VM was not successfull, i decided to wait for raz or others to > take a look before attempting to restart it as raz has vastly more knowledge and > experience and i didnt want to do more harm or loose information about what > happened. raz also failed to gather usefull information about the vm so he > restarted ffmpeg.org > the box came up as if nothing ever happened, we both looked over logs in search > of the cause, but came up empty handed. logs just ended Jul 26 22:47:14 which is > probably when the box did hang > all relevant packages where uptodate, the running kernel also seems to have > been the latest avalable for the ubuntu distrubution > > thx > > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Dictatorship naturally arises out of democracy, and the most aggravated > form of tyranny and slavery out of the most extreme liberty. -- Plato > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Observe your enemies, for they first find out your faults. -- Antisthenes [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-08-07 9:34 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-27 11:16 Michael Niedermayer 2022-08-07 9:33 ` Michael Niedermayer [this message] 2022-08-07 9:48 ` Timo Rothenpieler
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=20220807093356.GO2088045@pb2 \ --to=michael@niedermayer.cc \ --cc=Reimar.Doeffinger@gmx.de \ --cc=eclipse7@gmx.net \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=razor@blackwall.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git