Summit360

Thanks for that. It's a plausible thing given it's a 20year old dataset from various pre IPB setups. 

Going forwards, once the rebuild is complete, other than future rebuilds do the orphans cause any actual problems?

Also encountering this issue.

Just upgraded from 4.6.5 to 4.7.5.

Provisioned a new elastic cluster 7.10.2, old one was v6.# so incompatible.

1st rebuilt left no activity search results, second is generating pages of these errors.

Any solutions or things to try that can be shared?

None logged I think it just took a really long time, 5+ mins then the time for me to post here, so another 6 mins diff...

It's just completed ok. I'm going to chalk it up to one of those schrodinger internet cat things.

of course after waiting and waiting, as soon as i posted this... it only loaded the page...

Hi all,

This isn't the first time I've tried to do an update and been thwarted.

The upgrade process is basically stuck at sign in, so after step one confirm upgrade.

Just the spinner, no console errors.  Have signed in and out here a few times, plus in and out of the marketplace.

We've tried previous releases but it's always failed, we're told it's due to cloudflare. Well we're not behind cloudflare now and it's just as bad. 🙂

I'm tempted to do a manual upload but don't know if the upgrade needs to call home and as such we'd be blocked mid upgrade. FYI a test server idenitical setup has zero issues upgrading. Much confusion here 🙂

Anyone have any insight into what might be causing it to loop/hang... ?

On 7/29/2022 at 5:52 PM, Randy Calvert said:

Personally instead of trying to take the stick approach, I would try the carrot approach and contact IPS accounts and billing team PRIVATELY (https://invisioncommunity.com/contact-us/) and make your case there.

😄I was under the impression this was the mechanism to communicate with the team for support and get peer to peer advice. Previously it would of been private via the support system 😉

I'm not using a stick, I'm surprised is all. Thank you for your quoting, it will help many more I'm sure. I was being slightly sarcastic about the Eula back in 20##. Reflecting more in the change a company goes through as it evolves. I brought licenses to other software instead, the ipb ones will die with me. 

I don't believe the solution; as marked by Marc, is 'the solution'.

I wonder what the eula was when I purchased it all those years ago...

As Dean says, two parties, one dormant license to be reinvigorated, more revenue, another ipb community to potentially flourish.

Customers be like buffalo, loads one year, then gone tomorrow.

Yes that is unfortunate. 

I want to gift one of my dormant licenses to a team member.

I cannot see any way of doing it, various posts around the internet range from it's not possible, to it is possible.

Anyone any ideas on how to get this license handed over to my lovely volunteer to make his evening?

It's version 6, was fine... It was on 6Gb of 8Gb storage per node. guessing it didn't have enough storage to do the rebuild, just scaling it up to a larger storage... Still a good chance to find out a deployment isn't quite as tweaked as one hoped for 🙂

I'd say it's an elastic issue based on some system logs, although given that was ok before the upgrade... possibly an issue post.

IPS\Content\Search\Elastic\Exception (0) cluster_block_exception: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];

It's a hosted cluster for what it's worth. That's not quite hit my storage alarm, but has nonetheless, hit a problem. 

Would appear the assumption that all was well was mistimed. The rebuild got underway around 3hours ago and activity appeared to flow. However checking back in, the posts and unread content are all for nought since 3hours ago. 

In lieu of any other information, further assistance is required as this is the lifeblood of figuring out what's going on in the community. Thanks.

I removed it, refreshed, and then added it back in. 

Caching is afterall one of the two hardest things right...

Initial review seems to show a few users now. The old turn it off and on again trick worked. Onwards to the next niggle 🙂

Appreciate it might be cached, but there is a topic, quite a few that most users are on and it's been over 24hours.

It's been sat at zero all day for our site maintenance topic which, we push everyone to the day after an upgrade, more eyes etc.

Not stopping anyone from using the site, so will figure it out eventually.

The Registered users viewing the page block. We have it on topic page footers. This hasn't been tracking users on topics since the upgrade to 4.6.6. Was working fine before. Have gone through the something not working loop, no joy.

Reading the release notes for 4.6.6, guessing there is another job/task to be done to move this block on again?

Anyone any ideas?

Was going to raise something similar, I've noticed a slow admin screen since 4.5 and if anything it's slower in 4.6.6. Very much innodb and on a capable instance. 8/32.

Familiar with the mySQL docs. Rather assumed the format would be set in the schema during the migration. No matter done now. 

Just the duplicate key error on the row format conversion, see post : 

Principally the conversion to dynamic didn't solve it. The reindexing is underway, and activity is returning.

Dynamic is default on mariaDB 10.2, which is next on my long list of todo's. Well 10.1 > 10.3 🙂

So now just that one table and the duplicate entry problem to tackle 🙂

Confusing as we did the dynamic switch ages ago, so it looks like new tables created recently had the compact. Will check mysql config for a default value.

core_achievements_log
core_achievements_log_milestones
core_achievements_rules
core_anonymous_posts
core_badges
core_content_featured
core_item_member_map
core_member_badges
core_member_recognize
core_members_logins
core_notifications_pwa_keys
core_notifications_pwa_queue
core_points_log
nexus_invoice_tracker

core_achievements_log however falls over due to a duplicated key

ERROR 1062 (23000): Duplicate entry '132780.2021-09-16-core_SessionStartDaily' for key 'lookup'

Please advise, and or if this impacts the search index at all... which I'm poised to run now as my gut says none of these tables should be altering activity feed or posts behaviour.

Recently updated from 4.5 to 4.6 and the activity feed has all but stopped working. Post content is not appearing. Like reactions are. This is on default all activity at the endpoint of:

/discover

Is it likely to be the compact vs dynamic table issue?

Other suggestions?

I've slept on the email and on the first 14pages of this topic.  WOW!

12 month billing industry standard? Almost all of the services I use are per hour, per month, most offer an annual discount. Those that only have annual, TBH, they have something to fear to lock you in. Even microsoft do monthly 😉  who/what is a standard?  Be better by differentiating and offering your customers what they need.

Silver linings: I'm assuming search will be getting a really good overhaul, elastic 7? If we're to search for issues first. TBH I still just use `site:domain.tld` in google here and on my own sites. 

I can actually stand the price increases. But I'm not impressed at all, at how it's been done. Trust was a word used before, I'll reiterate that and add reputation. Now I don't want to renew on the principal of it, and to support those who had this foisted upon them. 

I understand the support changes too. As a developer of 25+years and engineering manager for many, I see my peers on support, their productivity is far lower. £ for £ I get more from my non-support folk. However, they tear through bugs, keep paying customers happy with super quick response times & prompt fixes. Sure we have the odd customer who is a 'burden' but we see it, if we can make it work for them, then 80% of the others won't bother us. Now if I could offload support to customers... win. #fail If multiple similar questions asked, add it to a knowledgebase, dev or customer led, #win.

Could also get rid of the annoying config/server queries by bumping the price up to a bearable, but mostly prohibitive figure? ...win. #fail Ultimately at $1250, that's an hour work a month I'd expect in return. Or one serious forum offline help me get it back. If I was raising that level of support queries, IPS isn't the best. I'd pay $100 per serious issue escalation or guaranteed resolution, not a sort it yourself as your not cloud hosted...

I didn't have premium support before, didn't feel I needed it, support was great; ok, mostly ok, a little difficult as self hosted, no sftp, 2fa etc for the dozen tickets or so over a decade. Had one bad upgrade, 4.5 to 4.6.6 yesterday ironically.

Community support no sla? That in essence, and at worst is, no support, a suggestion that breaks more than it fixes, an escalation to a ticket at some point/trigger?, or premium support! Well let's try it for a quarter, nowt to lose now.

I'd save a big chunk of my monthly going to your cloud offering, except I'd rather eat my own notebook. I choose to self host, I enjoy it and I can optimise it, tune it, debug it. Ican upgrade when it's not a buggy .0/.1 release.  I pay for an sla with service providers and pay for more with many companies whom I trust... who are open, transparent and fair. Who reward their evangelists and support the 3rd party community. 

not bad news... just wow.

On 7/9/2019 at 2:46 PM, Stuart Silvester said:

Elastic Search 7 isn't supported at this time, you will need to use version 5 or 6.

We will be adding support for v7, but I cannot confirm exactly when that will be yet.

+12 months any firmer ideas yet? 

Upgraded our test site. Only got a handful of users on it, but alas the achievements seems to be rather greedy.

1601133500% (32022670/2)

The  Rebuild achievements rule nexus_Subscription is just running and running. As it's a test site there is no support, but I can't find a way to stop this job from running. I've disabled achievements but it still gets picked up on the cron job and spins the server load up. Only a test server, but still would like to kill this job. I'm sure there used to be a bugs board or something on here too. 

I opted into the new achievements during the upgrade. I'd prefer not to delete all the rules as I was hoping to explore the new achievements. 

Anyone got an ideas?

Hi great work, looking forward to v3 for IPB4.5.

I'm currently warming some members up to it on the v2.4.7. Just learning all the new options and making a few minor tweaks.

One thing I can't quite seem to get right is the @mentions. That is I can make it right for light, but then dark looks out and vice versa.  I'd almost say no colour at all would be better.

I did look at the demo which seems to be making use of css vars 🙂 although they are not, or don't seem to be in 2.4.7.

Any thoughts on this one?