SmartActions does not work after server migration
K2 Server Migration: SmartActions Not Functioning - Resolved!
Problem: After migrating a K2 server, SmartActions stopped processing emails despite receiving replies in the designated mailbox.
Cause: The previous K2 server was still "running" in the new database, conflicting with the new server's SmartActions functionality.
Troubleshooting:
- Verbose HostServer logs revealed missing "Allocated" message for the SmartActions server, indicating the server wasn't designated for the task.
- Investigation discovered the previous K2 server (K2server1) persisted in the migrated database ("copy of K2database1") despite running in parallel with a different SmartActions account.
Resolution:
- Executed
server.kClusterDownon the "copy of K2database1" to shut down K2server1 within the database. - Manually removed references to K2server1 from relevant tables in the "copy of K2database1" database:
Server.ServerHostServer.ServerHostServer.LicenseKey
- Restarted the K2 service on the new server (K2server2).
Outcome:
- The "Allocated" message appeared in the HostServer log, confirming K2server2 as the designated SmartActions server.
- SmartActions processing resumed successfully.
Lessons Learned:
- Ensure a clean segregation of environments during database migrations to avoid conflicts.
- Utilize available logs and manual investigation to pinpoint root causes in complex issues.
Comments
Post a Comment