Yes, I'm facing (what can be termed as) a minor own server (ISPConfig3/Apache) issue as stated. Latest version of Elk (1.0.5). I have set 256MB for php which can be seen from php info; and Elk is 128MB, right? So what else could be the problem so that it can be looked into? Any suggestion?
You're probably running out of RAM with that little.
It could be literally anything...
But, if you have full access to the server, you could find a clue in the error logs somewhere (either apache or system) I think (I'm not a server guru, so I'm guessing :P).
Not so sure since this is not really a public server. RAM still good, i think.
Apache error logs will be checked later. Thanks
@emanuele .
I resolved this problem. Domain error logs provide clearer details if compared to Apache error logs. Problem is due xcache.
Is it a problem that can be fixed on Elk's side?
I am not so sure but in Apache error logs it was pointing to Cache.subs.php. but after checking the domain error logs, the problem is on xcache, so I fixed that by increasing memory for xcache.size and xcache.var_size.
How ElkArte actually takes advantage of this xcache or other caching softwares?
hmm... well, if it is a problem of memory I think it's outside of Elk's possibilities. Good because it means it's not a bug. :P
Storing info instead of doing queries. ;)
Lol... Right. Less database queries. But it seems by default, ElkArte has its own default file caching? WIll that work the same , if we don't have any external caching softwares installed?
File-based is an alternative in case there isn't a proper caching software installed on the server. But, is flawed since it's beginning and is meant to be removed.
Noted that.