I updated my ASG installation to 8.161, then imported an older 8.102 installation (to make sure some of the import bugs were worked out, related to old IM/P2P rule import issues)... I then enabled log management, which seemed to complete successfully. However, when I access Log Management from the button in the Webadmin GUI, the Log Management site shows No Devices available at all.
I don't know... I disabled it before I restored the 8.102 backup, then I enabled it again.
I'm in the Southeastern US, in the Eastern Time Zone (currently on Daylight Savings Time--what date and time do you want me to report... when I re-enabled it?
CTO, Convergent Information Security Solutions, LLC
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Got impatient waiting on another post here, so I just disabled and re-enabled Log Management.. this time the device shows up. I guess that some of the other fixes I've been seeing posted must have been the problem.
CTO, Convergent Information Security Solutions, LLC
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Sorry Bruce, this beta-run is a little bit different from the previous in that we are giving you multiple new products at once, with different teams working on it. We try to coordinate the work on the threads in a way, but i guess we're not good enough yet. Sometimes a threads goes out of sight...
I think you are right, there have been fixes in the Log Management backend servers, and maybe they fixed this problem too. I'll see Andreas tomorrow and have him take a look at this issue again.
I don't think this was related to the ASG update. A lot of LM related activity is does not affect the ASG and vice versa, therefore I'd also assume that the problem was caused by a hickup in the LM backend which is fixed in the meantime.
