Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Lookout 6.2 Beta
1 view
Skip to first unread message
erblock
Jul 24, 2008, 11:40:13 PM7/24/08
to
It appears that a Lookout 6.1 client process cannot display Hypertrend trace data generated by Lookout 6.2 Beta server process.
Existing server 6.1 database was off-line copied to new Lookout 6.2 directory on same server. Two issues notices so far:
1. On Lookout 6.2 Server machine, sqlservr.exe hogs ~50% CPU for over an hour now..... Restart....same. This did not happen with Lookout 6.1 & DSC 8.5 configuration.
2. Lookout 6.1 client hypertrends are not updating with server's Lookout 6.2 generated data. History from database is fine. Just in case... turned firewall OFF on both client and server....no change.
Ed
Existing server 6.1 database was off-line copied to new Lookout 6.2 directory on same server. Two issues notices so far:
1. On Lookout 6.2 Server machine, sqlservr.exe hogs ~50% CPU for over an hour now..... Restart....same. This did not happen with Lookout 6.1 & DSC 8.5 configuration.
2. Lookout 6.1 client hypertrends are not updating with server's Lookout 6.2 generated data. History from database is fine. Just in case... turned firewall OFF on both client and server....no change.
Ed
erblock
Jul 25, 2008, 1:40:08 AM7/25/08
to
Removed all NI software. Reinstalled 6.2 Beta, archived 6.1 data to 6.2 with MAX.
All OK. I did NOT copy the SQL files.
Hypertrend traces on 6.1 client now contiguous and sqlservr.exe is behaving fine....
Not sure if the original 6.2 install on top of 6.1 (w/ 8.5 DSC) went bad? May have just been directory change to Lookout 6.2 that messed everything up...
One thing I did notice after the uninstal of all NI software and subsequent reinstall of Lookout 6.2, the Lookout 6.1 service is still listed in services. This should have gone away, right?
Ed
All OK. I did NOT copy the SQL files.
Hypertrend traces on 6.1 client now contiguous and sqlservr.exe is behaving fine....
Not sure if the original 6.2 install on top of 6.1 (w/ 8.5 DSC) went bad? May have just been directory change to Lookout 6.2 that messed everything up...
One thing I did notice after the uninstal of all NI software and subsequent reinstall of Lookout 6.2, the Lookout 6.1 service is still listed in services. This should have gone away, right?
Ed
Ryan.S
Jul 28, 2008, 5:40:13 AM7/28/08
to
Thank you for testing Lookout.
Both case 1 and 2 should not happen.
Next time you see the 50% cpu usage of sqlservr.exe, close Lookout, and stop Citadel service, then check if it is still 50%. If it goes down, the problem is related to Citadel or Lookout, otherwise the problem is something else. You can also check if there are any abnormal event about SQL Server in Event Viewer.
We did some tests with Lookout 6.2 install upon previous version, but didn't see the similar problem. But from your description about the second issue, the Citadel may have something wrong after the install of 6.2. Before you install 6.2, lookout 6.1 and dsc 8.5 already installed on the same computer?
By the way, if it is a dual core cpu, 50% means full usage of one core. It is critical.
The Lookout 6.1 service problem is a bug. We are working on it.
Both case 1 and 2 should not happen.
Next time you see the 50% cpu usage of sqlservr.exe, close Lookout, and stop Citadel service, then check if it is still 50%. If it goes down, the problem is related to Citadel or Lookout, otherwise the problem is something else. You can also check if there are any abnormal event about SQL Server in Event Viewer.
We did some tests with Lookout 6.2 install upon previous version, but didn't see the similar problem. But from your description about the second issue, the Citadel may have something wrong after the install of 6.2. Before you install 6.2, lookout 6.1 and dsc 8.5 already installed on the same computer?
By the way, if it is a dual core cpu, 50% means full usage of one core. It is critical.
The Lookout 6.1 service problem is a bug. We are working on it.
0 new messages