I just went through the process to upgrade my LEM appliance to v5.5... all seemed to go well, except for the fact that when I browse to the web console, it still shows up as v5.4. how do i fix this?
Hey Kris, thanks for reporting this.
First, try refreshing (or closing/reopening).
Next, try clearing your browser cached objects for your LEM appliance (and refresh or close/reopen).
Next, try clearing your Flash Stored Objects for your LEM appliance - go to this URL to do that: Adobe - Flash Player : Settings Manager - Website Storage Settings panel (and refresh or close/reopen)
Let me know which one of these worked.
I opened my web console this morning, and suddenly it was prompting for a license agreement…it looks like it did the update sometime overnight, or a simple reboot of my pc fixed things. Thanks for your help!
Unfortunately, it seems as if some things are still not quite right though: when I open Explore --> nDepth, a big red message appears that says Error:General:FATAL: no Vertica user name specified in startup packet
What does that mean??? I seem to have lost the ability to look at historical data…
Hmm, interesting. Does it happen with every search? If you refresh the search (hit play again), do you see the same error? If you go to a filter in Monitor and do (on the top left) Gear > send to nDepth do you see the same error?
The error stays if I refresh the search, and it does happen with every search. Sending a filter to nDepth does the same thing.
Let's try first restarting the appliance. You'll have to go to the virtual console (or you can use SSH, let me know if you'd rather go that route) to do that.
To reboot, you can do a "send CTRL+ALT+DEL" to the VM for a soft reboot (please don't hard reboot ), or go to "Advanced Configuration", then type "appliance" (and hit enter), then "reboot" (and hit enter); confirm with the prompts and the appliance will reboot.
After that, try the searches again and let me know if it's gone.
It looks like a reboot resolved this. Thanks for your help. On the subject of reboots, is there some sort of high availability configuration that I can do with appliances so that if I have to reboot an appliance, I don’t lose log and event collection/actions?
The best solution for HA is to use the HA stuff built in to the hypervisor. We don't have a secondary HA service on the LEM side in favor of using what's built in.
But, useful to know, when the appliance is down:
That is all definetly very useful to know. What do you mean by use the HA built in to the hypervisor? VMWare won’t be able to provide HA when I only have one appliance… is there some sort of “scale out” deployment method that I should be doing?
