I have been getting a lot of these errors recently.

I've seen this in cases that the template disk cache is having write issues or that the cache is outdated. I would recommend inspecting whether or not that you require template disk caching if your server cannot write.

There are also quite a number of plugins/hooks being loaded for these errors that you may wish to check/disable and see if they are involved with this error.

4 minutes ago, Jim M said:

I've seen this in cases that the template disk cache is having write issues or that the cache is outdated. I would recommend inspecting whether or not that you require template disk caching if your server cannot write.

There are also quite a number of plugins/hooks being loaded for these errors that you may wish to check/disable and see if they are involved with this error.

There is no issue with read/write to the server.

I suspect this may be more down to a hook or php 8 specific issue, I will have another look to see if I can find the fault/issues. I was hoping that maybe someone else had come across this and help find a solution quicker. 🙂

1 minute ago, TDBF said:

There is no issue with read/write to the server.

To clarify, there may not be a write issue per say with permissions but the speed/performance may not be what is optimal in the time there so thus there is indeed a write performance issue. You can, of course, check this by disabling template disk cache as it will generate this on demand from the database instead.

@Jim M I was facing the same issue (we had literally thousands of those errors in our logs), and your advice to disable the template disk caching solved the issue for me. I only wonder if this is something more serious that must be addressed.

For those looking for this option: Advanced Configuration > Server Environment > Performance > Enable template disk caching?

Not sure if you are aware, but this was from 12 months ago

19 hours ago, Marc Stridgen said:

Not sure if you are aware, but this was from 12 months ago

@Marc Stridgen Yes, this topic is old but it helped me to solve the same issue I was having here. My question is whether I should investigate this further or not... Thanks!

Disk template caching will not be suitable in all environments. I would leave it switched off if things are working 

I have updated my IPB to 4.7.18 and get same errors:

What shoud I do to fix this?

You will want to check your System Log to see when the last time you actually logged those errors. That warning is simply stating that there are a lot of these which have been logged, not that it has been recently logged. If the upgrade resolved the issue, the warning would still be present as the logs have not been pruned yet.

No, these issues are new. They've got occured when I upgraded my IPB

I usually see this issue logged when the setting to cache templates to disk is enabled. Check, and if you have it enabled, try disabling it and the error should go away.

Unless you need it enabled for some reason? It usually causes only more trouble enabled, though. 🤷‍♂️

Yes, tempates disk cache is enable.

51 minutes ago, Seirei said:

Yes, tempates disk cache is enable.

Please disable that and let us know if that resolves the issue in the first instance

I clean all cache and this issue gone

1 minute ago, Seirei said:

I clean all cache and this issue gone

Likely some old, outdated cache that you encountered here when upgrading.

On 8/13/2024 at 4:13 PM, Marc said:

Please disable that and let us know if that resolves the issue in the first instance

I do not think this issue is about disk caching, but the fact that the data being saved is a false (boolean).

Looks to me that there is an issue elsewhere, and turning off disk caching doesn't fix the issue, but just prevents the error. This issue only started after the core updated to 8.1.

I haven't had a chance to actually debug this issue further, but what I have seen, I don't think turning off disk caching is the actual solution to this issue.

10 minutes ago, TDBF said:

I haven't had a chance to actually debug this issue further, but what I have seen, I don't think turning off disk caching is the actual solution to this issue.

This is a temporary check. You can delete the template cache on your disk and then re-enable it to see if the issue is still present. If it's not, then likely outdated cache that due to the upgrade, created the problem. (i.e. the template that was cached was updated and thus broke the template).

Has anyone found a solution for 
 

`TypeError: flock(): Argument #1 ($stream) must be of type resource, bool given.`

disable `template cache on your disk` is not solution

 

16 minutes ago, grek29 said:

Has anyone found a solution for 
 

`TypeError: flock(): Argument #1 ($stream) must be of type resource, bool given.`

disable `template cache on your disk` is not solution

 

There is a bug report in for this 🙂