I just did some digging in the logs, and I see this when I try to remove someone from a group they shouldnt be in:
... 15 more
at com.mysql.jdbc.PreparedStatement.executeBatchedInserts(PreparedStatement.java:1 714)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructor AccessorImpl.java:45)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessor Impl.java:57)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'fromJIDResource' in 'field list'
at org.jivesoftware.openfire.archive.ConversationManager$1.run(ConversationManager .java:190)
at org.jivesoftware.openfire.archive.ConversationManager$ArchivingTask.run(Convers ationManager.java:1010)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:43)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at com.mysql.jdbc.PreparedStatement.executeBatchedInserts(PreparedStatement.java:1 760)
java.sql.BatchUpdateException: Unknown column 'fromJIDResource' in 'field list'
2017.02.07 08:54:54 org.jivesoftware.openfire.archive.ConversationManager - Unknown column 'fromJIDResource' in 'field list'
Something is definitely going on. Every time I go into my "Groups" tab it's random. Problem users revert back to normal, normal users become problem users. What the hell is going on with my group sharing & how do I fix it?
Can you confirm that incorrect groups affiliation is actually showing on the client and not just in Admin Console? There were reports of Admin Console showing wrong information since 4.1.0.
The best I can give you is "maybe". I have had some users tell me they are now only seeing the groups they belong to, others are telling me they have a new "unfiled users" group they've never seen before. I also know that manipulating the groups while users are logged in wreaks havoc with the roster. On my own Spark install if I moved user A into Group 1 & then look at the roster, it gives the appearance of the corrupted groups.
Those users maybe saw the result of you fixing the groups (as you say, changing groups while users are logged creates a mess in the client until it relogins). So, don't do anything to the seemingly bad groups/users and wait for reports or ask users next day if they see problems.
I'm now getting calls/complaints about inconsistent rosters. Numerous users now log in and only see the group they are assigned to and not all shared groups. I'm at the point now where I'm going to just rip the server out and fully rebuild it from scratch as I don't get what is happening.
If I reboot the server on everyone when I get a complaint it seems to "fix" it.
Are the shared groups in rosters a know issue?
1 of 1 people found this helpful
I think your option for now is to downgrade to 4.0.x version. There is a ticket for an issue when it only affects Admin Console [OF-1269] Admin Console shows wrong group affiliation information for some users - IgniteRealtime JIRA I think only this ticket is closest to your issue (but it seems it was an older issue than 4.1.x, maybe just it happens more often now) [OF-1263] Contact List sharing shows stale data - IgniteRealtime JIRA
I'll give this a shot momentarily. Just have to grab a 4.0x .deb file for my server & I can get this taken care of. Thanks!