Forum Activity for @brian

Restoring a profile - gallery items not restored.

Using Jamroom


Yep - that makes sense - gallery images are not part of a "group" and are really individual entries in the gallery datastore that are grouped by profile_id/gallery_name.

I'll check it out and see if that can be supported (the "restore" in the recycle bin is fairly complicated).

Thanks!

maybe an issue with latest beta core

Installation and Configuration

It sounds like your sitemap crawler could be spawning a NEW session for every page load, which in turn could be filling your session table up with thousands and thousands of unnecessary entries.

Try running:


From like phpMyAdmin (or whatever you use for DB management). Let me know the number of sessions in your session table.

Restoring a profile - gallery items not restored.

Using Jamroom

Glad to see that restored for you.

If I understand what you are looking for, it's that when a gallery is deleted (but NOT the profile), the gallery items are going in to the Recycle Bin and in order to restore the entire gallery you have to do it one at a time - does that sound right?

Thanks!

Restoring a profile - gallery items not restored.

Using Jamroom


I see the account in the Recycle Bin - does it not restore for you?

maybe an issue with latest beta core

Installation and Configuration

If you can't even run an integrity check without a server crash, something is really messed up. I don't believe I have ever seen that on any site we manage.

maybe an issue with latest beta core

Installation and Configuration

As long as you haven't recently cleared caches, you should be ~75% hit rate easily.

Are you running any other sites on your server except the Jamroom server? With the amount of RAM you currently have (I'm not sure how many CPUs you have) you should have no issues - it should have no problem handling hundreds of simultaneous users and even hundreds of bots at the same time.

maybe an issue with latest beta core

Installation and Configuration

The editor in comments issue was fixed a couple betas back - make sure you are running 6.5.0b2.

maybe an issue with latest beta core

Installation and Configuration

And this one:


Means your redis server disconnected before the READ could occur - again, not a Jamroom issue.

If your site is REALLY busy, you could be running into a maxconn issue - make sure and check this out:

https://www.cyberciti.biz/faq/ip_conntrack-table-ful-dropping-packet-error/

Do some reading about how the kernel handles IP connection tracking - you may need to increase it.

maybe an issue with latest beta core

Installation and Configuration

There is no need to post any "MySQL server has gone away" errors - that's not a Jamroom issue.

maybe an issue with latest beta core

Installation and Configuration

Note that we do not develop or test on Litespeed - just an FYI.