9

Well, quite - as I said upthread…

This smells of more than just TTRSS running on that server.

10

tt-rss is not somehow unique in its ability to insert data into a database so this isn’t in any way related to tt-rss (or any other database client) per se.

if this issue really does exist as described (i’m not convinced still) this should be reported to mysql and maybe distro maintainers because inability to deal with inserts without restarting seems like a critical problem.

in any case, OP made the thread here, so if other people run into this issue with tt-rss specifically they should be able to find a solution. i’m not going to update any documentation because of this, however.

e: does tt-rss even use temp tables? not explicitly that’s for sure.

11

I just figured I would post this to try and get it added.

I wiped one of my servers and installed tt-rss (love it btw), some plugins and a mysql search.

In about a week with me viewing it everyday, I started getting out of memory errors, to the point it kind of broke tt-rss (nothing would work and was getting gui errors)

Did some research and found that the innodb file expanded to my whole drive, only way to fix it was to restart the service, and set a cap to prevent it in the future.

This was the exact error it caused
https://tt-rss.org/oldforum/viewtopic.php?t=2608

NOTE Error only, not related to thread title, or resolution (well it was never resolved for him)

12

That post relates to RAM, whereas you’ve been talking about disk space this entire time.

13

The thing is its not caused by ram, its the same error if you run out of disk space

14

Sure, but when you say, “This was the exact error it caused,” and link to a thread that’s discussing out of RAM issues… It’s misleading and could confuse others. Your issue is distinct from the issue in that thread.

15

But it is the exact error I was getting.

I understand your point and I’ll edit it to reflect error only, but do you think it would help if I stole their image as well? Havent gotten this error in awhile so I cant make a new one.

Also, him adjusting his memory never fully resolved the issue.

16

I tend to think that the PHP memory error is unrelated if only because, based on your posts so far, there isn’t an issue with PHP. The issue is with MySQL running out of disk space, that should cause MySQL to fail and PHP (I should think) would report a failure with the database.

Now PHP could have a memory or disk error because TT-RSS does write to disk, etc. but without seeing the actual error message for your particular issue it would be difficult to diagnose.

Keep an eye on your system and post with an error from your system if one ends up occurring.

17

As I stated before.

That is the exact error message I was receiving.

The photo in the other thread, 100% verbatim

18

The error message might be the same but the location at which the error occurs will likely be different, and that’s the information that’s going to help resolve it.

Like I said, keep an eye on your system and post with an error from your system if one ends up occurring.

19

I’m not a MySQL guy, so take this with a grain of salt. If this issue is related to temporary tables/files/etc in MySQL consuming all available disk space, MySQL could be treating that as “virtual memory” (like an OS treats swap). If the database is unable to store more information in that “swap” area, and if the database treats this swap area as virtual “memory”, then it may report an out of memory error back to PHP.

If that’s what’s going on, it could explain why this out of disk issue manifests as an out of memory error in the tt-rss logs. What do the MySQL logs say?

But as I said, I’m not a MySQL guy (viva PostgreSQL).

20

As I also already stated, I resolved it by capping how large the temp file can grow.

This post is literally just asking if they could include that in the setup instructions.

The InnoDB temp files only grows, it does not shrink. It will eventually grow to use all available disk space unless MySQL is restarted.

The config option I was proposing to have included in the install guide is to limit how much the temp file can grow instead of letting it consume the whole disk.

21

But it should not grow to use all available disk space (according to the documentation), unless there is a bug somewhere or there are temporary tables created, that are that large. That space is used by mysql also for internal temporary tables. https://dev.mysql.com/doc/refman/8.0/en/internal-temporary-tables.html. I guess, that it is possible, that such tables could remain around in case of long-running transactions/connections.

22

You are correct, its not suppose to.

But seeing how it was a fresh install of ubuntu server 16.04 with only tt-rss + a hand full of plugins installed.

Something related to tt-rss made it grow, hence why I suggest capping the temp files.

10GB is excessive but I dont know how much was needed, seems to be sitting around 6GB for me for the past 2 months

23

More interesting is, how many feeds are you subscribed to? (my psql database is btw < 1GB and I have quite a few feeds, so I’m interested how your temp file is growing that large)

I never used Mysql as I prefer the foss version MariaDB, but this really is no problem of tt-rss (and most likely not intended by the developers of Mysql).
Drawing an analogy, you are also not provided with a driving license if you are buying a car. So this does not belong to the installation guide and might confuse some people installing with MariaDB or PostgreSQL.

24

only 51, deleted a few when it first happened and never re-added them

25

MySQL version 8 is neither in 16.04 nor 18.04 in the ubuntu main repository.
Do you really use something like MySQL from the universe repo in a server installation ???
Perhaps you should read the support guidlines for the universe repository and think about your decition of your software usage.

My ttrss-inst runs on Lubuntu 18.04LTS with mysql-5.7 and php-7.2. I have 177 subscriptions in 20 categories.

mysql mysql 6.9K Aug 27 19:26 ib_buffer_pool
mysql mysql 138M Sep 6 12:39 ibdata1
mysql mysql 48M Sep 6 12:39 ib_logfile0
mysql mysql 48M Sep 6 12:39 ib_logfile1
mysql mysql 76M Sep 6 12:39 ibtmp1

26

That was just a link to MySQL man page referencing how Innodb works.

We are actually running the save version

-rw-r----- 1 mysql mysql 17K Aug 28 10:29 ./ib_buffer_pool
-rw-r----- 1 mysql mysql 76M Sep 6 07:26 ./ibdata1
-rw-r----- 1 mysql mysql 48M Sep 6 07:26 ./ib_logfile0
-rw-r----- 1 mysql mysql 48M Sep 6 07:24 ./ib_logfile1
-rw-r----- 1 mysql mysql 6.7G Sep 6 07:25 ./ibtmp1

27

As someone who has been running TT-RSS for years with MySQL and over 300+ feeds, together with several other services on a single VPS all using MySQL for databases with InnoDB tables very actively, and disk usage monitoring set on my mysql directories I can contribute the following information:

  • I’m currently running the same MySQL server version
  • My ibtmp file never grew larger than 76MB according to my disk usage reports

As a professional I feel I should point out that:

  • if you’re setting a max size of 10G for it while it has been growing to 40G, all queries that are either explicit or internal temp table will fail once the need to go over 10G is reached, which usually renders the application in an unusable state due to unexpected database errors
  • internal innodb temp tables will grow the file only if the available memory and/or buffer sizes are not adequately available / configured, which tells me the correlation with your PHP memory errors does not necessarily imply causation
  • MySQL’s logging features are your friend

Also @jeremyrem, what TT-RSS version are you running and which plugins (since you’ve explicitly mentioned it) ? For all I know you’ve got some custom plugin running that’s solely responsible for all your troubles.

28

I didn’t find a solution on this forum regarding huge disk usage by ttrss mysql db, so I hope this will help:

mysq -u root

alter table ttrss.ttrss_entries force;

got it from here