u/lorenzo1142

I'm watching my web server logs tonight, looking for any bots abusing things. here's something new I've never seen before, google bots pretending to be all kinds of other bots, and 100-200 requests within only a few seconds.

it came from 2 different google IP addresses, first 211 requests within 16 seconds, then a half hour later 131 more requests within 3 seconds. the agent for these requests say Bravebot, GrokBot, DeepSeekBot, Kimi-SearchBot, YouBot, YiBot, Amazonbot, PanguBot, MoonshotBot.... and many others.

it's unlike google to send this many requests within such a short time. could it be some google AI bot going crazy?

does anyone here use SchematicsForFree .com ? the reliability of the website has been lacking this year, and I know some people want a copy of all the files, so I made a torrent of the entire collection. when more content gets added, I'll make a new torrent. the torrent is available for free on the website, it just needs some seeders.

it's a little more than 50 gigs

This subreddit needs proper moderation. I have been trying to contact the mods for the last 3 years. The subreddit is now being spammed with "server finder" and no mods are around to do anything about it.

I would love to help revitalize this subreddit.

I have a 15 year old supermicro 2U server, which I bought used and have been using for the last 10 or so years. I seem to be having some hardware failure, so it's time for upgrades.

I'm planning to keep the same CSE-825 case and swap out the motherboard. I'm thinking probably LGA2011 socket with dual cpu support. start with a single cpu and have the option to expand later. my budget is around $300 for used hardware.

I'm planning a new backrooms minecraft server, but will probably use folia, so it might be better to go with more cpu cores instead of faster per core. I do run other things on the same server, but minecraft is the biggest resource demand. the worlds are huge and players spread out, so folia should be perfect for this, with plenty of cpu cores.

maybe 16+ cores at 2.3Ghz base would be the best option for me? I'm looking for the best value, and still good performance. once I pick a cpu, I have to find the right motherboard to fit my needs. I would definitely like to stick with supermicro.

I will need to replace my old ddr3 ram with ddr4, 16 gig ecc sticks. and a new HBA card, probably either 9300 or 9400, something under $100 used. I don't need sas, I only have sata drives with a sata backplane.

I'm in need of some guidance and suggestions. everything follows the cpu, so I don't want to make a mistake from the starting point.

---

if you care to know how my last 2 weeks have been:

I finally switched to fiber internet tuesday of last week. I have had nothing but problems with my server ever since. before this, I was going on a full year of uptime. server couldn't get an IP from my internet provider. finally figured out the dumb mistake I was making after a week. network is working, next problem...

my 30TB zpool somehow got corrupted. after rebooting it somehow freed up 800 gigs, I think just some removed snapshots that failed to free up space. that's fine, but now every time I try to write to the zpool it causes some weird sync error, the kernel hangs, and the zpool itself goes suspended. I think importing the zpool as read only seems to be stable, so I'm hoping can still recover from this.

there are no disk checksum errors. smart says all the drives are good. I've ruled out problems with the old HBA cards, the backplane, the drives, cables, power supplies, ram, heat, kernel and zfs versions.... I've even tried the latest bleeding edge kernel and zfs versions, always the same problem, zpool goes suspended and kernel hangs.

so I've disconnected the disk drives for now and running only on an ssd connected to the onboard sata. yesterday it hung again.... okay, so maybe the onboard sata is the problem? so now I have the ssd connected to a HBA card. I look over just now and it hung again.

at the moment I'm using a small fanless computer as a temporary server to get back online. I run opnsense in a vm. last night, that fanless computer crashed with IO errors..... that has never happened before and I have no idea why it crashed. is the government blasting me with microwaves or something??

it seems likely to be a zfs bug. but, I would still like to upgrade my dated hardware.

I need to make some custom packages for my servers and containers, for a few different distros. I've grown tired of fighting with all the different tools and the special ways they do things... Fine, I'll make yet another standard to rule all standards!..

My goal is to Keep It Simple Stupid. I don't want custom binary formats or 1000 line spec files or a special package for each distro... Just keep it simple.

A package is a zstd compressed tar with a json metadata file and the payload. The package repositories are indexed and stored as json in a normal package. Can't get much simpler than that. Fetch the latest index package and the cache is all up to date.

Creating a package, indexing packages, and installing/updating packages, all done with the same tool. One package should work on any linux distro, and it works along side existing package managers.

It's not finished, but I've gotten a lot done, and it's about ready to start testing before production use. I'm starting out using it in docker as install only, no updating. Next I will add support for tracking of installed packages and updating, and dependencies and all that. I made it in golang and wrote all the code myself. It will be released as AGPL open source.

What do you think, sound useful?

I want to make my own package manager for linux, in golang. Anyone want to help or even just chat about it?

I've been researching the topic for about a week. I'm still fuzzy on how some things should work. Here's what I plan so far:

A package will be a zstd compressed tar archive, with a file extension of box, or maybe bocks. Inside it will be a json file for metadata, a file for signing, and the payload files to be installed. The payload files don't need to be in any specific directory path, they can be wherever is convenient for development. The final path is decided by the json metadata at the time of actual install.

The package repository index will be a package itself, containing an index.json file, with searchable fields. When you want to install a new package repo, or when the package manager wants to update the cached index, it's as simple as downloading the index package and installing or updating it in the local system.

My goal is, Keep It Simple Stupid. I need to make packages for a few different types of systems, and I'm tired of fighting with spec files and abuild and whatever else. I just want a simple package manager which I can use along side whatever the distro uses by default.

Sound interesting? Want to help or chat about it?