Hi! Please help with tips!
I have Openfire 4.7.5 with users from 6 group of domain that work fine, but when I upgrade to 4.9.2, one of group dissapear on Spark and I don’t understand why, see captures.
After several attempts, I realized that the problem is with some files in the “lib” directory.
If I copy entire “lib” directory from Openfire 4.7.5 to openfire 4.9.2, without overwriting any file, then I see all 6 groups but admin console it doesn’t work anymore.
That’s weird. I wouldn’t know what could cause this. Are you using something like LDAP or AD, or are these groups defined in Openfire itself?
Try enabling trace logging, and then see if your logs contain any reference to the ‘missing’ group name after you’ve used the system for a while.
Hi, that’s right, weird. I have this groups on AD and I use LDAP on Openfire to grab it. It’s clearly not a configuration problem. I’ve been using the same configuration for several years and have done several Openfire version updates without any problems.
If I’m not mistaken, I had problems when I wanted to update to 4.8.3, but I’ve only just now studied the problem and noticed the strangeness with the files in the “lib” directory
I try with overwrite files from “lib” directory from 4.7.5 to 4.9.2 with same result: after copy I see all groups but no web admin console. Same result with upgrade to nightbuild 5.0 from 12.03.2025.
The strange thing is that the group with problems is seen but the users in it are not seen.
Overwriting lib directory content with data is very likely to give inconsistent results. I recommend against doing that.
What makes the affected group different from other groups?
As I suggested earlier: try to enable ‘trace’ logging, and see if you can find any references to the ‘missing’ group.
Hi!
Trace logging dont help me. Anyway I was able to fix the problem that was somehow inside the database. The problem persists even on a new server with a new installation of Openfire
After several tests on a production-based test environment, I discovered that the problem was resolved by disabling sharing between groups and reactivating them.
