Re: [FFmpeg-devel] Previous trac server hosting Was: STF RaptorQ

[Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>]

On Sat, 24 May 2025, 17:39 Michael Niedermayer, <michael@niedermayer.cc>
wrote:

> Hi
>
> On Fri, May 23, 2025 at 01:13:05PM +0100, Kieran Kunhya via ffmpeg-devel
> wrote:
> [...]
> > > As an example i could have instead replied with a tone matching yours:
> > > (below is a (true) example of communication in the same tone as yours
> > >  that i avoid)
> > >
> > > "I appreciated the stellar service you provided by providing and
> > >  hosting a trac server for FFmpeg. It had only one broken cpu core.
> > >  You only once decided to use the FFmpeg server to test some random
> > >  audio hardware.
> > >
> > >  Its sad that our users need reliable service"
> > >
> >
> > You seem to forget that you contacted me in a panic because your hosting
> > was gone. And I went into the office on a Saturday in my own time and
> found
> > the first server I could find and immediately set it up for you. You are
> > very much welcome for this.
>
> Its long ago, if we look at the logs, we can see how the whole team worked
> together with no problems and then votes are started on people and fail and
> you shut the server down.
> This log is sadly a bit lengthy, i tried to cut away uninterresting things
> but its still long.
>
> When it all started in 2015
>
> Jul 04 15:39:34 *       kierank (sid5955@gateway/web/
> irccloud.com/x-jxtnzgbwhhjmsyes) has joined ##ffmpeg-admin
> Jul 04 15:39:43 <kierank>       I have a box with 2x 750GB drives
> Jul 04 15:39:49 <kierank>       and 250mbit/s internet
> Jul 04 15:40:58 <michaelni>     hi kierank maybe we could move trac there
> and or secondary nameserver i dont know if anyone is working on trac rescue
> Jul 04 15:41:18 <michaelni>     if you know trac, ive no idea what you know
> Jul 04 15:41:43 <kierank>       I can try migrating trac
>
>
> First surprise, secure login:
>
> Jul 04 21:00:50 <kierank>       217.138.67.134 - username: ffmpeg
> password: ffmpegpassw0rd
> Jul 04 21:00:52 <kierank>       you can login
>
>
> Later we learn more about the machiene:
>
> Jul 06 23:49:53 <kierank>       that server has some oddities like
> Jul 06 23:49:54 <kierank>       CPU 4 on socket 0 has large number of
> corrected cache errors in Level-2 Generic
> Jul 06 23:49:54 <kierank>       System operating correctly
> Jul 06 23:51:42 <beastd>        ah
> Jul 06 23:53:17 <michaelni>     kierank, can you replace faulty hw ?
> Jul 06 23:53:45 <kierank>       yes there are 4 machines which I think are
> identical
> Jul 06 23:54:07 <michaelni>     rcombs, and others will that ipv6 mail
> stuff not cause problems without reverse dns, or do we have reverse dns ?
> Jul 06 23:55:07 <kierank>       there are also a ton of uniprocessor
> machines there
> Jul 06 23:55:50 <michaelni>     kierank, please replace that faulty cpu if
> you can easily, i dont think this is urgent but its better to replace if
> you can easily
> Jul 06 23:55:58 <kierank>       it's not easily replaceable
> Jul 06 23:56:06 <michaelni>     :(
> Jul 06 23:56:26 <kierank>       I'm not sure if I could just pull the
> disks out of one and stick it in another machine
> Jul 06 23:56:28 <kierank>       because of the raid
> Jul 06 23:56:51 <kierank>       the OS seems to have disabled the faulty
> cores
>
>
> ECC RAM vs backups for db ?
>
> Jul 07 01:00:51 <kierank>       Error Correction Type: None
> Jul 07 01:00:52 <kierank>       apparently not
> Jul 07 01:01:28 <kierank>       hence why it should get backed up
>
>
> "tons of other boxes" there ...
>
> Jul 31 17:33:57 <TimNich>       If we could get a better box at your loc,
> that would be good wouldn’t it?
> Jul 31 17:34:46 <kierank>       yes, there are tons of other boxes, just
> haven't had time to see what's on them yet
>
>
> replacing a disk: "doesn't boot at all now"
>
> Feb 20 15:36:58 <kierank>       I found a spare hdd
> Feb 20 16:07:15 <kierank>       so looks like /dev/sda has failed
> Feb 20 16:07:26 <kierank>       need to figure out how to remove it from
> the raid array and add /dev/sdb
> Feb 20 16:20:55 <kierank>       ok going to take trac down
> Feb 20 16:33:21 <kierank>       back up but using the bad disk still
> Feb 20 16:33:53 <michaelni>     what went wrong ?
> Feb 20 16:34:17 <michaelni>     or it was intended to still use the old ?
> Feb 20 16:37:09 <kierank>       it wasn't happy with the new
> Feb 20 16:37:19 <kierank>       and now it wants to raid resync
> Feb 20 16:37:22 <kierank>       which is going really slow
> Feb 20 16:42:39 <michaelni>     why didnt it accept it? do you have
> another disk ?
> Feb 20 16:43:11 <kierank>       I have to let it raid resync now
> Feb 20 16:43:31 <kierank>       I think there was some stuff on that disk
> which confused it
> Feb 20 16:43:35 <kierank>       so I am wiping the new disk
> Feb 20 16:43:43 <michaelni>     ahh, ok
> Feb 20 16:43:53 <kierank>       the raid resync will take a day or so
> Feb 20 16:43:56 <kierank>       it's about 1x in
> Feb 20 16:43:58 <kierank>       1%
> Feb 20 16:45:21 <kierank>       trac is hanging which I don't like
> Feb 20 16:45:56 <michaelni>     :(
> Feb 20 16:48:48 <kierank>       seems up but slow
> Feb 20 16:50:15 <kierank>       basically got to wait for the existing
> raid to sort itself out
> Feb 20 16:50:19 <kierank>       and hopefully not cause any damage
> Feb 20 16:50:30 <kierank>       and then I can swap /dev/sda for /dev/sdc
> Feb 20 16:50:34 <kierank>       and see if that works
> Feb 20 16:50:41 <kierank>       otherwise i'll swap /dev/sdac
> Feb 20 16:50:51 <kierank>       otherwise i'll swap /dev/sdb for /dev/sda
> Feb 20 16:50:54 <kierank>       and put /dev/sdc in /dev/sdb
> Feb 20 18:04:40 *       Disconnected (Input/output error).
> **** ENDING LOGGING AT Sat Feb 20 18:04:40 2016
>
> **** BEGIN LOGGING AT Sat Feb 20 18:05:17 2016
>
> Feb 20 18:05:17 *       Now talking on ##ffmpeg-admin
> Feb 20 18:07:07 <michaelni>     kierank, just be carefull you dont
> overwrite the good disk from an empty one
> Feb 20 18:07:47 <kierank>       I'm hoping the raid controller will do the
> right thing
> Feb 20 18:07:49 <kierank>       but not fully sure
> ...
> Feb 21 15:09:15 <kierank>       don't know but I can put a new disk in
> Feb 21 15:09:21 <kierank>       "new"
> Feb 21 15:10:23 <michaelni>     if putting a "new" disk in + sync fixes it
> it would be easier than a full reinstall i guess
> Feb 21 15:10:51 <kierank>       ok I will try
> Feb 21 15:15:10 <kierank>       well it doesn't want to rebuild to the new
> drive
> Feb 21 15:15:48 <michaelni>     what does it say to what command ?
> Feb 21 15:18:04 <kierank>       root@ffmpeg1:~# dmraid -s
> Feb 21 15:18:04 <kierank>       ERROR: isw: wrong number of devices in
> RAID set "isw_ciaehhaddg_RAID1" [1/2] on /dev/sdb
> Feb 21 15:18:04 <kierank>       ERROR: isw: wrong number of devices in
> RAID set "isw_dageddcdde_Volume0" [1/2] on /dev/sda
> Feb 21 15:18:04 <kierank>       *** Group superset isw_ciaehhaddg
> Feb 21 15:18:04 <kierank>       --> *Inconsistent* Subset
> Feb 21 15:18:04 <kierank>       name   : isw_ciaehhaddg_RAID1
> Feb 21 15:18:04 <kierank>       size   : 1465143296
> Feb 21 15:18:05 <kierank>       stride : 128
> Feb 21 15:18:05 <kierank>       type   : mirror
> Feb 21 15:18:06 <kierank>       status : inconsistent
> Feb 21 15:18:06 <kierank>       subsets: 0
> Feb 21 15:18:07 <kierank>       devs   : 1
> Feb 21 15:18:07 <kierank>       spares : 0
> Feb 21 15:18:08 <kierank>       *** Group superset isw_dageddcdde
> Feb 21 15:18:40 <kierank>       this machine uses ubuntu "fakeraid"
> Feb 21 15:21:09 <michaelni>     ill try to research that a bit, you can
> also ask root@ffmpeg.org someone like raz or arpi should know what to do
> Feb 21 15:22:31 <kierank>       should be rebuilding now onto new disk
> Feb 21 15:32:23 <kierank>       game over
> Feb 21 15:32:24 <kierank>       doesn't boot at all now
>
>
> wait for admins or just wipe and reinstall
>
> Feb 21 15:43:18 <michaelni>     i mailed the log to root, maybe one of
> them has an idea
> Feb 21 15:44:46 <kierank>       I am reinstalling
> Feb 21 15:44:51 <kierank>       it's too late
>
>
> Secure login #2
>
> Feb 21 16:14:28 <kierank>       ok you can login to uk trac
> Feb 21 16:14:31 <kierank>       username: ffmpeg
> Feb 21 16:14:36 <kierank>       password: ffmpegPassw0rd
> Feb 21 16:14:56 <kierank>       michaelni: ^
> ...
> Feb 21 16:31:18 <michaelni>     also its safer to just add my key to
> authorized_keys than using pw
> Feb 21 16:31:26 <michaelni>     ssh-rsa ...
>
>
> what 250mbit/sec really means
>
> May 18 01:14:52 <kierank>       I may have to ratelimit connectivity on my
> FFmpeg machine soon
> ...
> May 24 20:21:44 <kierank>       traffic shaping on my machine to 5mbit/s
> up and down for now
>

The server was moved away at this time. It was doing purely backups.

...
>
>
> ending hosting after a vote doesnt go as planned:
>
> So 12 Jun 2016 22:58:37 CEST Paul B Mahol <onemda@gmail.com>
> [FFmpeg-devel] [VOTE] Ban Carl Eugen Hoyos
>
> **** BEGIN LOGGING AT Mon Jun 13 05:54:31 2016
> Jun 13 12:24:21 <kierank>       I am considering taking fftrac-gb offline
> Jun 13 13:01:36 <kierank>       permanently
> Jun 13 13:25:44 <michaelni>     kierank, why ?
> Jun 13 13:25:58 <michaelni>     we use the machine
> Jun 13 13:27:31 <kierank>       ffmpeg is a sinking ship
> Jun 13 13:35:46 <michaelni>     kierank, whats the matter all of a sudden ?
> Jun 13 13:36:04 <kierank>       look at ffmpeg, the community is falling
> apart
> Jun 13 13:36:34 <michaelni>     taking the server offline is not going to
> help the situation
> Jun 13 13:36:55 <michaelni>     everyone overreacts already
> Jun 13 13:36:57 <kierank>       i've told you for 9 months now to let vlc
> host us
> ...
> Jun 13 13:48:39 <kierank>       nobody voted for me to host
> Jun 13 13:50:25 <michaelni>     no, you generously offered it, we needed
> to move and it seemed a good choice to accept, noone objected AFAIK and
> time was rather short
> Jun 13 14:03:59 <michaelni>     also i think you know derek well, is there
> something that can be done to get him to return?
> Jun 13 14:05:38 <michaelni>     that 4month vote was very unwise as peope
> will not support it due to harshness
> Jun 13 14:17:57 <michaelni>     kierank, ^ (do you have an idea how we can
> get derek back?)
> Jun 15 21:25:25 <kierank>       my server is going down
> Jun 15 21:25:27 <kierank>       bye
> Jun 15 21:25:44 <kierank>       can't really support the insanity of this
> project atm
> Jun 15 21:36:02 <michaelni>     kierank, please explain
> Jun 15 21:37:30 *       kierank (sid5955@gateway/web/
> irccloud.com/x-alaucxykftiixsxj) has left ##ffmpeg-admin
>

You had already moved trac from this server at the time.

I helped you in an emergency in my own spare time on a Saturday. I found
the first server I could to get trac back.

It's truly incredible getting lectured from you on being a sysadmin.

Adding cc as quotes are being taken out of context here when I helped the
project in my own spare time on a Saturday in an emergency.

I will quote Anton here:

"
Behold, the favorite excuse of every tin-pot dictator ever.

So boiling down your verbal vomit, I get

    Yes, your democracy IS just pretend and I - the person who

    * tries very very hard to avoid as much human contact as possible
    * oversaw one of the most toxic FOSS communities for close
      to 25 years
    * through heavy-handed authoritarianism directly caused one of the
      most notorious forks in FOSS history

    really do know better than everyone else how to run a community.


To that I say:
* you are delusional, as you are the source or enabler of all the
  toxicity
* Libav had NONE of these problems (not saying it was perfect - it did
  have other problems, but not these)
* there is no hope for this project as long as you continue to hold the
  reins and I've wasted enough of my life on it.
"

He is absolutely spot on.

Kieran
_______________________________________________
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".