Re: New Cumulus Home
Posted: Tue 06 Nov 2018 7:31 pm
That is awful
Are you able to tell me the date/time of occurrence (UTC)?
Thanks,
Support forum for Cumulus weather station software
https://cumulus.hosiene.co.uk/
That is awful
Thanks for highlighting this. I have checked against server (both web and db) performance for the time period 18:00 UTC to 18:08 UTC (based on the timing of this post) and the metrics I see don't suggest a problem with the servers themselves (relatively low CPU - some spikes on db, but that is normal - and memory usage well within physical memory settings) so I am puzzled at the moment. I need to collect some more data.weatherist34 wrote: ↑Tue 06 Nov 2018 6:08 pm yes i agree something is better than nothing but in comparison to any other forum,new forum site is painfully slow to actually use almost to point of (as harsh as that sounds) unuseable. i guess start up teeting issues and works ok for some and not good some .
just now
20 second login aprox
click on this post another 30 seconds to appear for reading
click on post reply another 20 seconds to get to window
total aprox 70 seconds to get to the reply form ,thats before typing a response/reply
i find it quicker to read post not logged in as they appear instantanousely .
just really highlighing the issue not being un appreciative for the offering of this site and im sure with some closer inspection of code/configuration it will get resolved. FWIW three years ago i migrated a hotel portal to a new domain very similar start up issues and slow performance eventually traced down to three hardcoded scripts to the old domain <script src= http://oldmain.com/somejquery.js> for example .not saying thats the issue but until looking closer we would never have discovered it has it wasnt flagged in the console error logs as the old domain was still active.
ps i had to edit after posting another 30 seconds to get back to here.
Code: Select all
If you still want to use it for registrations but not for submitting a post then open /posting.php and find:
CODE: SELECT ALL
// DNSBL check
if ($config['check_dnsbl'] && !$refresh)
{
if (($dnsbl = $user->check_dnsbl('post')) !== false)
{
$error[] = sprintf($user->lang['IP_BLACKLISTED'], $user->ip, $dnsbl[1]);
}
}
Ah okay thanks - I didn't read the article, I just knew that the setting was off. If that is the code in use then I will never turn it onConligWX wrote: ↑Tue 06 Nov 2018 8:10 pmthat was in the link I provided. so if blacklisting is on it check for user registrations AND posts.Code: Select all
If you still want to use it for registrations but not for submitting a post then open /posting.php and find: CODE: SELECT ALL // DNSBL check if ($config['check_dnsbl'] && !$refresh) { if (($dnsbl = $user->check_dnsbl('post')) !== false) { $error[] = sprintf($user->lang['IP_BLACKLISTED'], $user->ip, $dnsbl[1]); } }
I have made some adjustments (more resources for both web and database server, and a change to the network topology between the two) and am currently assessing those changes. I tend to gradually tweak so I can understand the implications of each tweak.