Lookout 6.2, Citadel Crash

Ok, beating a dead horse... I think we are definitely getting to the end of our NI lifespan
Background
System installed with Lookout 6.1 in 2008, ran well for about 1.5 years. Random crashes, database corruption, etc. Initially believed to have been the machine (Software RAID 5 sucks). New machine built in Oct. 2010; no RAID, Intel Core2 machine, XP SP3. Upgraded to Lookout 6.2. Could not import the 6.1 database, performance slowed to a crawl, believed to be from a corrupt database. Created a new database.
Today
Machine is experiencing system failures on Citadel and Lookout. We have nothing but AlarmDialer 4 (custom notification software), RealVNC Enterprise, Lookout 6.2, HP Printer and standard system related tools (TrueImage, AVG, Adobe Reader (Latest version, for manuals)) installed on this machine. All updates installed.
Latest Windows Mini-dumps: http://support.forshock.com/files/MRCWD/Minidump.zip
Latest (related) error messages:
Event Type: Error
Event Source: SQLBrowser
Event Category: None
Event ID: 1
Date: 12/21/2010
Time: 5:27:46 PM
User: N/A
Computer: SCADA
Description:
The SQL configuration for SQL is inaccessible or invalid.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 4d 00 53 00 53 00 51 00 M.S.S.Q.
0008: 4c 00 53 00 65 00 72 00 L.S.e.r.
0010: 76 00 65 00 72 00 5c 00 v.e.r.\.
0018: 43 00 75 00 72 00 72 00 C.u.r.r.
0020: 65 00 6e 00 74 00 56 00 e.n.t.V.
0028: 65 00 72 00 73 00 69 00 e.r.s.i.
0030: 6f 00 6e 00 00 00 o.n...
Event Type: ErrorEvent Source: SQLBrowserEvent Category: NoneEvent ID: 1Date: 12/21/2010Time: 5:27:46 PMUser: N/AComputer: SCADADescription:The SQL configuration for SQL is inaccessible or invalid.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 4d 00 53 00 53 00 51 00 M.S.S.Q.0008: 4c 00 53 00 65 00 72 00 L.S.e.r.0010: 76 00 65 00 72 00 5c 00 v.e.r.\.0018: 43 00 75 00 72 00 72 00 C.u.r.r.0020: 65 00 6e 00 74 00 56 00 e.n.t.V.0028: 65 00 72 00 73 00 69 00 e.r.s.i.0030: 6f 00 6e 00 00 00 o.n...
Event Type: Information
Event Source: MSSQL$CITADEL
Event Category: (2)
Event ID: 26037
Date: 12/21/2010
Time: 10:01:26 AM
User: N/A
Computer: SCADA
Description:
The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: b5 65 00 00 0a 00 00 00 µe......
0008: 0e 00 00 00 53 00 43 00 ....S.C.
0010: 41 00 44 00 41 00 5c 00 A.D.A.\.
0018: 43 00 49 00 54 00 41 00 C.I.T.A.
0020: 44 00 45 00 4c 00 00 00 D.E.L...
0028: 00 00 00 00 ....
We get lots of these entries:
Event Type: Information
Event Source: MSSQL$CITADEL
Event Category: (2)
Event ID: 17401
Date: 12/21/2010
Time: 1:44:58 PM
User: N/A
Computer: SCADA
Description:
Server resumed execution after being idle 10079 seconds: user activity awakened the server. This is an informational message only. No user action is required.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: f9 43 00 00 0a 00 00 00 ùC......
0008: 0e 00 00 00 53 00 43 00 ....S.C.
0010: 41 00 44 00 41 00 5c 00 A.D.A.\.
0018: 43 00 49 00 54 00 41 00 C.I.T.A.
0020: 44 00 45 00 4c 00 00 00 D.E.L...
0028: 00 00 00 00 ....
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 12/22/2010
Time: 7:29:18 AM
User: N/A
Computer: SCADA
Description:
Faulting application lookout.exe, version 6.2.0.49153, faulting module nicitmid.dll, version 5.6.0.49153, fault address 0x00069ffb.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6c 6f 6f ure loo
0018: 6b 6f 75 74 2e 65 78 65 kout.exe
0020: 20 36 2e 32 2e 30 2e 34 6.2.0.4
0028: 39 31 35 33 20 69 6e 20 9153 in
0030: 6e 69 63 69 74 6d 69 64 nicitmid
0038: 2e 64 6c 6c 20 35 2e 36 .dll 5.6
0040: 2e 30 2e 34 39 31 35 33 .0.49153
0048: 20 61 74 20 6f 66 66 73 at offs
0050: 65 74 20 30 30 30 36 39 et 00069
0058: 66 66 62 0d 0a ffb..
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/21/2010
Time: 5:28:15 PM
User: N/A
Computer: SCADA
Description:
Error code 00000024, parameter1 001902fe, parameter2 b9cebbbc, parameter3 b9ceb8b8, parameter4 b965a667.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 32 0000002
0020: 34 20 20 50 61 72 61 6d 4 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 31 39 30 32 66 65 2c 20 1902fe,
0038: 62 39 63 65 62 62 62 63 b9cebbbc
0040: 2c 20 62 39 63 65 62 38 , b9ceb8
0048: 62 38 2c 20 62 39 36 35 b8, b965
0050: 61 36 36 37 a667
Forshock - Consult.Develop.Solve.

Year later. We have a system with approximately 8.05GB in citadel. System shutdown, restart. Database is now taking over 1 hour to "rebuild" and is not complete. Secondary has 7.99GB, same issue.
Processes will not function, system is sluggish, basically useless.
Long live Citadel...
Forshock - Consult.Develop.Solve.

Similar Messages

Lookout 6.5 critical crash - writes to random modbus addresses

Hello,
We are experiencing a rather critical problem with Lookout 6.5. The proces file contains approximately 148 Modbus/TCP connections, some overview panels, a properties panel which uses a symbolic link to retrieve properties from a certain modbus object.
Seemingly random, Lookout crashes during operation (with the Windows send/don't send window). When this happens, the second before the crash actually occurs Lookout starts writing seemingly random values to addresses to all the modbus devices. Some to addresses which are connected in Lookout, and to some that are not (even to addresses that actually don't exist on the device, which causes it to return an exception). The addresses do seem to be in an increasing sequence (i.e. it starts at 500, then starts writing further until about 850). Values I've seen are mostly 0, but also 256, 2308, 512, 2048, 3844.
I've attached a packet capture log which shows the write commands Lookout is sending.
Does anyone have any idea what could cause this crash or things I can check?
Attachments:
dump.txt ‏175 KB

Also uploaded a second dump file as Randomwritecrash2.zip - I'll keep uploading dump files in sequence.
Crash data from this dump:
(1328.bd4): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=01cbcd1a ebx=00f70000 ecx=3e720012 edx=3e720013 esi=00f70838 edi=00000009
eip=7c902a9d esp=0013f4f4 ebp=00f70838 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010202
ntdll!tan+0xcf:
7c902a9d 8b18 mov ebx,dword ptr [eax] ds:0023:01cbcd1a=????????
0:000> kb
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
0013f4f8 7c91020e 00000009 00f70838 00f70000 ntdll!tan+0xcf
0013f510 7c9101db 0013f744 7c90e920 7c910228 ntdll!RtlAllocateHeap+0x14a
0013f528 7c91019b 00f70838 00000013 0000003f ntdll!RtlAllocateHeap+0x117
*** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\WINDOWS\system32\MSVCR71.dll -
0013f754 7c3416b3 00f70000 00000000 0000003f ntdll!RtlAllocateHeap+0xd7
0013f794 7c3416db 0000003f 7c3416f8 0000003f MSVCR71!_crtLCMapStringA+0x305
00000000 00000000 00000000 00000000 00000000 MSVCR71!_crtLCMapStringA+0x32d

Lookout 6.0 and Citadel 5 Slow to Connect and Display Data

Wondering if anyone else is seeing this.
We had a Lookout 5.1 Citadel 4 database running about 75-100 data points. We use hypertrends for viewing the trended data. In the old version, the hypertrends and historical data would be presented on the screen nearly instantaneously. We recently upgraded to Lookout 6.0 and Citadel 5. The hypertrends now take minutes to display and often times come in choppy. This is VERY inconvenient, especially when we try to connect other clients over our T1 WAN connection.....display time is VERY long.
I don't want to update our other Lookout system to 6.0 until this issue is resolved, our other system has a database that has somewhere in the realm of 3000+ data points it is tracking, and we can't afford to lose the speed for the trending displays.
Thanks for any input in advance.

I complained to ni about the fact that nicitdl5 is using a lot of processor resources on the computer running the server process. As an answer I received the same bla bla ... more robust ... bla bla. The thing is that it is happening only when the client is accessing the server from the network. When they are on the same computer every thing is fine. I think it is more of a communication problem. You can use the performance monitor to graph the network activity of nicitdl5 to see that it is receiving a lot of packets while sending almost nothing. That leads me to the hypothesis that the client is making a lot of useless request (buggy hyper.cbx?) to the citadel server.
Still, I'm reassured to see that I'm not alone facing that performance issue but I think that we'll have to wait for 6.1!

Write to Citadel database from LabVIEW?

Hi. I'm a newbie when it comes to Lookout and the Citadel database... so here's my question for you all:
We have various labview applications that log data from instruments. We would like to be able to take this data and store it as "tags" in a Citadel database.
What do you think is the best way to do this?
There are ODBC drivers for the Citadel database, but they appear to only allow you to query the database to retrieve values... you can't write data to the database (so its read-only).
Are they any "Lookout VIs" or Citadel VIs that can write to the Citadel DB from LabVIEW? Or a DLL or something?
Any ideas?
regards,
John Paul

Very nice question John Paul. I take it you already have Lookout and LabVIEW. In this case, with the latest versions of either, simply use the LabVIEW datasocket to publish the items on your front panel. Lookout then can subscribe to these once you register the LabVIEW computer. Once you have subscribed to them in Lookout, you are then able to set up logging. You may need to create an expression object to route the data to citadel.
If you just want to use LabVIEW and the Citadel database, you might try VI Logger. This works in our configuration utility - MAX, and also comes with a set of VIs for LabVIEW. One caveot, the Citadel database in VI logger is newer (and faster) than the Citadel database in Lookout. I believe NI is working to synchronize
the version in the future, and its hard to say when. So till then, you would not be able to merge data in the dislike citadel databases. However, you can always use and ODBC call set to extract from both and store in a more permanent SQL database such as access, oracle, ms back office, etc.
Good Luck,
Preston Johnson
Business Development Manager
Industrial Applications
National Instruments
Preston Johnson
Principal Sales Engineer
Condition Monitoring Systems
Vibration Analyst III - www.vibinst.org, www.mobiusinstitute.com
National Instruments
[email protected]
www.ni.com/mcm
www.ni.com/soundandvibration
www.ni.com/biganalogdata
512-683-5444

Lookout 6.5 new Logon/Logoff feature does not save

I am excited to see that Lookout 6.5 has a new Logon/Logoff feature - but I am having minimal success with it. I am running Lookout 6.5 Integrator on a new Windows 7 Professional PC. If I go to $System Connections and double-click on the Logon Writeable member, Lookout goes dim and crashes. Once I have restarted lookout and go back into $System Connections, if I type "Logon" into the Select field and click on Select, then I can connect to a pushbutton, and the connection is confirmed in the Existing Connections list. The connection works - I can bring up the Logon window with the pushbutton. So far so good. One of the first things I notice is when I make this connection an asterisk (denoting a change in the file) does NOT appear beside the process file name on the top of the Lookout window. If I go to File\Save - Save is not bold - indicating there is no change in the file. If I go to File/Save As - I can save the process file but the Logon connection is not saved. If I shutdown Lookout and restart the process file - the Logon connection is not there. ????
Solved!
Go to Solution.

Thanks for your help, Ryan.
I find that by using a pushbutton and editing its remote source to the Logon, the pushbutton works (brings up the Logon window) but the pushbutton stays depressed.
As a work-around, I've used a sequencer fired by the pushbutton; sequencer output A is connected to the Logon, then a second later sequencer output B gives a FALSE to the pushbutton to make it pop back out. To connect the Logon to the sequencer output, I manually edited the .lks file with the required text, then re-compiled the process file. It s bit of a devious route, but now it works good.
Thanks.

Android Web Client Capability?

Any chance of getting access to Lookout and/or citadel data through an Android phone (web client, app, or other)?

Here is how we have done it before.
The lookout process is set as seperate client & server processes. Create a virtual machine (or another system) running Remote Desktop, Lookout Client and the client process. Setup your users in remote desktop and lookout.
Go to android market place and get PocketCloud (free would work to test). Connect to the virtual machine with Remote Desktop and view the client process.
Keeps clients from directly conencting on the production machine, for Pro versions you bypass the 1 session limit for desktop, user management is simplified (lookout).
Good luck,
Mike
Forshock - Consult.Develop.Solve.

Were are the "error logs" saved to?

Were are the "error Logs" saved to. My Lookout 6.0 system crashed last night for no appearent reason, other than the building A/C unit went out and the room became very hot. The PC that is running Lookout was still operating and the call-out system running on it notified me that Lookout was down. I started the system back up with no problems.

Hello,
The only place where you can see what happen would be in the Event Viewer from your Windows computer. Go to Control Panel, Administrative Tools, and you will see in there the Event Viewers. Hope this helps
Ricardo

Lookout Client V6.0.2 keeps crashing - lkwrks.dll problem

On several of my machines running the Lookout client version (6.0.2 with updates), Lookout consistently crashes. Below is the information from Event Viewer:
Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date:  4/3/2007
Time:  12:40:46 PM
User:  N/A
Computer: SCADA-SD
Description:
Faulting application lookout.exe, version 6.0.2.1, faulting module lkworks.dll, version 6.0.2.1, fault address 0x00021c5b.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 6c 6f 6f   ure loo
0018: 6b 6f 75 74 2e 65 78 65   kout.exe
0020: 20 36 2e 30 2e 32 2e 31    6.0.2.1
0028: 20 69 6e 20 6c 6b 77 6f    in lkwo
0030: 72 6b 73 2e 64 6c 6c 20   rks.dll
0038: 36 2e 30 2e 32 2e 31 20   6.0.2.1
0040: 61 74 20 6f 66 66 73 65   at offse
0048: 74 20 30 30 30 32 31 63   t 00021c
0050: 35 62 0d 0a                       5b..
Again, this is only happening on machines running the Client version.
All machines are Dells running Windows XP SP2 and have at least 1 GB of RAM.
Please respond A.S.A.P.
Thanks!
Jason Phillips

I am aware of the fact that you cannot copy the updated lkworks.dll file to the client version - if you do you will get an "evalutaion version" dialogue box everytime you open the client.
This problem is occuring with all of the updated files, except "lkworks.dll", copied to the Lookout 6.0 folder.
I found out late yesterday afternoon that this crash is occuring on machines running the client version and running my client process file. On machines running the client version but not running the client process file, the crash does not occur. For example, I have one machine running the client version and a logging process file which does not crash. Also, on machines running the server version and the client process file, the crash does not occur. So, it appears that the problem has to do with machines running the client version and the client process file. This process file is much bigger than the logging file I had previously mentioned, about 11Mb. Attached are my client and server files to assist you in diagnosing and correcting this problem.
Please respond A.S.A.P.
Thanks!
Jason Phillips

Remote Lookout Citadel connections with Labview 8.6

What is the cleanest method to import remote computer citadel data and/or live Lookout process data members into Labview 8.6. Data Socket or Shared Variables or ... ?
Thanks,
Ed

If you use shared variable or datasocket, it doesn't read data from the citadel database, but all are live data directly from the remote tag. Shared variable is better.
If you want to read data from the citadel database, read trace.vi can help you. Or use hypertrend to view the historical or live data trend.
Ryan Shi
National Instruments

Options to edit historical data in Citadel database (Lookout 6.0)

We are running a new installation of Lookout 6.0
I am looking for ways to edit the historical data that is found in the Citadel database. For example, if an alarm clears before I can enter comments, I would like to go to the database after the fact and enter comments regarding the alarm.
We are running this on XP pro operating system.
Thanks,
Alan

Hi Alan,
I am afraid this will be difficult, if at all possible. Citadel data, by design, can be written to (and edited?) only by the product using it, i.e., Lookout, LabVIEW-DSC, etc. Outside of these products we can only retrieve the data -- not edit or add to it. As you are probably aware, some of the options for writing user data (as opposed to IO/system data) from within these products is to use the Logger Object in Lookout and the VI-Server approach in DSC (http://zone.ni.com/devzone/conceptd.nsf/webmain/5a921a403438390f86256b9700809a53).
So, I guess one option is to "annotate" / write additional data separately using the Logger Object, referencing the Alarms somehow.
Having said that, I believe Lookout 6.x (Citadel5) uses MSDE for storing Alarm data (other data is still stored in the native Citadel database). You could explore this -- try opening the MSDE database from Query Analyzer, from instance, and see if it can be edited. I haven't tried this.
Hope this gives you some ideas.
-Khalid

What exactly do the national instruments citadel nt service and the lookout citadel nt service run

We have WhatsUp monitoring software set to monitor NI Lookout and the PC it is on. It pings the PC, and polls the Lookout Citadel Server NT service. If either one fails, WhatsUp sends an email notification. I was under the impression if the Lookout Citadel Server service is down, then NI Lookout won't graph or record data, but that's not the case. If I shut Lookout Citadel Server or National Instruments Citadel Server down, NI Lookout still graphs and records. What exactly do these two services run?
Also, is there a possibility that NI Lookout can be viewed through palm OS software, like a Blackberry?

Lookout Citadel Server is for Citadel 4, which is used by Lookout 5 and DSC 7.
NI Citadel is for Citadel 5, used by Lookout 6 and DSC 8.
If Citadel is stopped, Lookout will start it up automatically when launched. But if Citadel is stopped when Lookout is running, there might be some unexpected issues, although the data logging seems to be working well.
So I strongely recommend you not to stop those Citadel service when Lookout is running.
Lookout cannot be running on palm OS.
Ryan Shi
National Instruments

How To Stop Lookout Web Client Crashing IE Web Browser

Hi,
I am using Web Client with Lookout. My problem is I can only load a panel within Internet Explorer once. If I reload the URL within the same session then Internet Explorer crashes.
Can anyone offer me advice to fix this problem please?
Software is as follows:
- Lookout V 6.0 (build 5)
- Browser: Internet Explorer 6.0.28
- Web Server: Tomcat 5.5.7
The steps I took are as follows:
1. Created Process
2. Set up File-> Web Server Options->Export Directory to:
c:\telemetrysms\webapps\root\user\fishfarmlive\
(where “c:\telemetrysms\webapps” is Tomcat webapps folder)
Set up server URL to:
http://HOSTNAME/user/fishfarmlive/
(where “HOSTNAME” is the server name)
3. Export Web Server Files
4. Start IE and open web page. My panel displays correctly (with live data), although the only alarm Lookout displays is “The remote position source is not writable”.
5. HOWEVER, when I reload the page in IE the browser will always go blank for several seconds and then crash (with no error message).
Furthermore…
As a test I created a simple test process with nothing but one panel containing a single line of static text. This simple project also crashes.
This computer also has Lookout 5.1 installed. And projects created in 5.1 only crash the browser very occasionally.
Any suggestions (about the crashes or the missing alarms) would be greatly appreciated?
Thanks.
Regards Brett Sheeran

Brett,
I have some info for you regarding the web client. I am including links to two documents that have information that will help you with your problem. The first document is good info about developing a web client application and the second has information directly pertaining to the IE crash that is occurring. It also has other troubleshooting information. I would also recommend checking the firewall on the computer. It windows security settings also have to be set to low in order for web client to communicate correctly.
Deploying a Lookout Application
Lookout Web Client Troubleshooting
Regards,
Danny G
Applications Engineer
National Instruments

I have Lookout 6.5 running with Windows 7, the process has been running for about 2 months with no problems, but today the Citadel stopped working! I am having a hard time getting it started again, need help!

I have Lookout 6.5 running with Windows 7, the process has been running for about 2 months with no problems, but today the Citadel stopped working!
How could this have happened and what can I do to get it running again?

Didnt realize there was a response, late getting back to you.
Save your process files outside of the NI progam directory (you should have external backups already right ). THey should not be deleted.
Any customizations to the lookout.ini and lookout.sec file may be lost.
Mike
Forshock - Consult.Develop.Solve.

Why does reopening Lookout 5.1 build 8 once a day stop radio polling crashes?

Polling 9 sites by radio has resulted in almost daily stoppage of Lookout process. At that time nothing is polled and the process stops taking in new information. To fix the problem the process must be reopened. While trying a fix, it was noted that if we reopened the process once a day before stoppages, that there would be no stoppage. Is this an issue only with Lookout 5.1?

I guess the fix you said is the one on the NI website.
Do you mean you were told by the fix that "if we reopened the process once a day before stoppages, that there would be no stoppage"?
We first need to locate where the problem is. So, which driver object do you use in your process?
Do you log the data to Citadel database?
Ryan Shi
National Instruments

Display archived citadel data mixed with "live" Lookout machine data using Hypertrend object?

Maybe a new feature request item?
It would be really nice if you could use a Hypertrend object in Lookout to plot historical data from an archived Citadel database. So this would be a feature where you could connect an additional (or many) additional databases as machine processes in (read only mode of course). This would allow mixing display objects (trends) of running processes along with display objects (trends) of archived "processes" in the same Hypertrend display when using Hypertrend in the historical mode.
The Lookout Hypertrend object is awesome and it is about time you folks gave Lookout some attention again to exploit its power and coolness.
Thanks and Happy New Year!!

The hypertrend use Citadel service to transfer the data between computer, while the live data is different, so your problem is probably in networking setting or firewall.
If you have firewall on either computer, follow these KBs.
http://digital.ni.com/public.nsf/allkb/0D7B86F4B4D19A5E86256F9A006EECB1?OpenDocument
http://digital.ni.com/public.nsf/websearch/8AE45BBFA1D7025E862570F200642FD8?OpenDocument
Lookout client software doesn't install MAX.exe, but if you have MAX.exe on the client computer, you can use MAX to check the connection. In MAX, try to view the remote trace.
You can also use the NI Hypertrend ActiveX object to check the connection. Create a client process with just a NI Hypertrend ActiveX object. Move it to client computer. Edit its properties and add a trace, then try to view the remote trace. See the attached screenshot. If the Citadel communication has problem, you will not see the database or the trace.
The ActiveX object doesn't fix the problem, but can tell you whether the remote connection is good or not.
Message Edited by Ryan.S on 11-14-2008 03:49 AM
Ryan Shi
National Instruments
Attachments:
1.JPG ‏71 KB

Lookout 6.2, Citadel Crash

Similar Messages

Maybe you are looking for