We have a situation that after migrated the APM Server from 6.2 to 6.5 session storage absolute path is not accepting.
We created a new SAN storage and moved the data from the existing location to the new location.
Your early assistance will be highly appreciable, thanks.
Thank you for your comments.
In the existing server the absolute path was working but on the new server after every restart the server path changes as a default.
I am also opening the support case as you suggested due to production environment.
Is there any way that we can sync/merge two different Session Storages?
As long as the system profiles are the same, you should have no problem moving the data from one session store to a new location, however, the behavior of reverting back to default is strange, and is usually seen in situations where changes are made to config files while the server is running, but the session store location does not fall in that category, the new location is being accepted and applied, correct?
Thank you for your reply.
Yes. On the first stage it accepts and ask to restart to take the effect but after restart it is keep changing to the default settings even in the existing server the setting was absolute.
In the server logs following messages appeared.
Line 5140: 2017-03-23 21:30:05 WARNING [Server] Unable to initialize the stored session manager. Error: null
Line 5141: 2017-03-23 21:30:05 WARNING [Server] Stored Session directory "G:\appmon65\server\sessions\stored" was reset to the default stored session directory: sessions/stored
It is automatically changing the into following location.
Line 5150: 2017-03-23 21:30:06 INFO [FileBasedSessionManager] Initializing stored session manager, storage directory: E:\appmon65\server\sessions\stored
Copy from support ticket fix for reference:
The specificied storage location needs to be accessible by the user with which the AppMon server windows service is running (per default the user "Local Service").