Skip to main content


Well, apart from the fact that:
Enabling SSL kills the site.
It moans "table_open_cache too low (400)" when it's actually set to 2000
#Friendica is back
in reply to utzer [Friendica]

Sadly I blotted my copybook with the maintainer. I doubt I'll get any help there, and I've no desire to be told to "Fuck Off" again. #LeSigh
in reply to Shredni Vashtar

@Peter Cannon not sure what you mean, but as said great support can be found in !Friendica Support, about the SSL, there is nothing special about that for Friendica, so just find some nice description on how to set it up for you system and webserver. There is so many unkowns that it is hard to support, you need to find some description that comes close to your setup.
in reply to utzer [Friendica]

I accused the developer of ignoring my posts. In my defence, I was pretty frustrated at the time.
in reply to Shredni Vashtar

@Peter Cannon say sorry, we're all human, frustration is understandable, but should not overcome you when looking for help. I think you should just write a post in the same group and write this and that you're sorry. Pretty easy I think, as you already realized you fault.
in reply to Shredni Vashtar

Friendica does really require a reasonably well tuned database to function speedily, but https verses http really should not have any bearing on that. Suggest using the latest mariadb and follow instructions on their site for tuning. My database previously maxed out at 400 TPS, now it can handle spikes of 10,000 TPS, mostly by following instructions there. This only made a small difference for friendica but a huge difference for hubzilla which is not so well crafted in terms of it's database use (in particular it does a lot of large unindexed searches). For best results, don't try to run on a machine with just a few gigabytes of RAM, MariaDB works best when it mostly works out of memory which means throwing a lot of memory at it.
Unknown parent

Shredni Vashtar
It does.

Your table_definition_cache is too low (400).
in reply to Shredni Vashtar

It is the latest on a brand new LAMP server hosted at work (We're an independent ISP)
MySQL / MariaDB
max_allowed_packet 16777216
in reply to Shredni Vashtar

@Peter Cannon 16 MB of packet size is OK and should work, some GIF and some posts will not be stored than, but if you can live with that it is fine. I found myself setting it higher and using a even higher number for a mysqldump (backup), as it seems I have some huge packets stored in my database.
in reply to utzer [Friendica]

You'll be please to know I fixed the table_definition_cache is too low error by doing:
sudo vim /etc/mysql/mariadb.cnf


[mysqld]table_definition_cache = 1500
sudo systemctl restart mysqld

What figure do you suggest for max_allowed_packet?
in reply to Shredni Vashtar

@Peter Cannon for max_allowed_packet is is hard to say, I just checked, for some reason I had it set to 256M, but that is too much. It is, as far as I understand, the maximum size that can sent/written to the database, so based on that, 32M or 64M should be plenty. Just my guess.

I think Steffen know better than I.
in reply to utzer [Friendica]

@utzer @Peter Cannon I have mine set at 4G, I don't see any reason ever for a packet to be that big but lots of RAM so no good reason to limit it.
in reply to Nanook

@Robert Dinse I think it is unusual big and might not be very good, it could cause that huge files are stored in the DB. @Peter Cannon
in reply to Nanook

@Robert Dinse @Peter Cannon I doubt that there is any legit files this big, but maybe someone could DDoS you by that. I don't mind that you set it like that, but I think it is not good idea.
in reply to utzer [Friendica]

@utzer @Peter Cannon I don't see how. They could not transmit 4G files fast enough to DOS, really it takes UDP or ICMP for a good DOS as TCP is self regulating.