Azure IoT Hub device twins with AMQP usable already? - azure-iot-hub

I cloned the newest version of the Azure C-SDK. One of the recent commit messages says that device twins over AMQP were added. I tried to switch the devicetwin_simplesample.c of the serializer samples to AMQP:
git diff devicetwin_simplesample/devicetwin_simplesample.c
diff --git a/serializer/samples/devicetwin_simplesample/devicetwin_simplesample.c b/serializer/samples/devicetwin_simplesample/devicetwin_simplesample.c
index 7da717c..d390a25 100644
--- a/serializer/samples/devicetwin_simplesample/devicetwin_simplesample.c
+++ b/serializer/samples/devicetwin_simplesample/devicetwin_simplesample.c
## -14,7 +14,7 ##
/*String containing Hostname, Device Id & Device Key in the format: */
/* "HostName=<host_name>;DeviceId=<device_id>;SharedAccessKey=<device_key>" */
-static const char* connectionString = "HostName=...";
+static const char* connectionString = "HostName=XXXX.azure-devices.net;DeviceId=XXXX;SharedAccessKey=XXXX";
// Define the Model - it is a car.
BEGIN_NAMESPACE(Contoso);
## -47,6 +47,7 ## DECLARE_DEVICETWIN_MODEL(Car,
WITH_REPORTED_PROPERTY(Maker, maker), /*this is a structured reported property*/
WITH_REPORTED_PROPERTY(CarState, state), /*this is a model in model*/
+ WITH_DESIRED_PROPERTY(CarSettings, settings) /*this is a model in model*/
WITH_DESIRED_PROPERTY(CarSettings, settings), /*this is a model in model*/
WITH_METHOD(getCarVIN)
);
## -101,7 +102,7 ## void device_twin_simple_sample_run(void)
else
{
/*create an IoTHub client*/
- IOTHUB_CLIENT_HANDLE iotHubClientHandle = IoTHubClient_CreateFromConnectionString(connectionString, MQTT_Protocol); // Change to AMQP_Procotol if desired.
+ IOTHUB_CLIENT_HANDLE iotHubClientHandle = IoTHubClient_CreateFromConnectionString(connectionString, AMQP_Protocol); // Change to AMQP_Procotol if desired.
if (iotHubClientHandle == NULL)
{
printf("Failure creating IoTHubClient handle");
It compiles. When I start it, however, I get the following error and the application quits immediately:
Info: IoT Hub SDK for C, version 1.1.21
Info: Retry policy set (5, timeout = 0)
Error: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_common.c Func:IoTHubTransport_AMQP_Common_Subscribe_DeviceMethod Line:1720 Not implemented
Error: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/iothub_client/src/iothub_client_ll.c Func:IoTHubClient_LL_SetDeviceMethodCallback_Ex Line:1854 IoTHubTransport_Subscribe_DeviceMethod failed
Error: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/iothub_client/src/iothub_client.c Func:IoTHubClient_SetDeviceMethodCallback Line:1619 IoTHubClient_LL_SetDeviceMethodCallback_Ex failed
Error: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/serializer/inc/serializer_devicetwin.h Func:Generic_IoTHubClient_SetCallbacks Line:193 failure in IoTHubClient_SetDeviceMethodCallback
Error: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/serializer/inc/serializer_devicetwin.h Func:IoTHubDeviceTwinCreate_Impl Line:261 failure in Generic_IoTHubClient_SetCallbacks
Failure in IoTHubDeviceTwin_CreateCarError: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/serializer/inc/serializer_devicetwin.h Func:IoTHubDeviceTwin_Destroy_Impl Line:306 invalid argument void* model=(nil)
Info: Transport state changed from AMQP_TRANSPORT_STATE_NOT_CONNECTED to AMQP_TRANSPORT_STATE_CONNECTING
Info: Transport state changed from AMQP_TRANSPORT_STATE_CONNECTING to AMQP_TRANSPORT_STATE_CONNECTED
Info: Transport state changed from AMQP_TRANSPORT_STATE_CONNECTED to AMQP_TRANSPORT_STATE_BEING_DESTROYED
Error: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/uamqp/src/amqp_management.c Func:amqp_management_close Line:888 AMQP management instance not open
Error: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_connection.c Func:on_cbs_open_complete Line:149 CBS open failed
Error: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/iothub_client/src/iothubtransport_amqp_cbs_auth.c Func:on_cbs_put_token_complete_callback Line:188 CBS reported status code 0, error: '(null)' for put-token operation for device ''
Error: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/uamqp/src/saslclientio.c Func:saslclientio_send_async Line:1165 send called while not open
Error: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/uamqp/src/connection.c Func:on_bytes_encoded Line:241 Cannot send encoded bytes
Info: Closing tlsio from a state other than TLSIO_STATE_EXT_OPEN or TLSIO_STATE_EXT_ERROR
Error: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/uamqp/src/saslclientio.c Func:on_underlying_io_open_complete Line:178 Open complete received in unexpected state
-> [CLOSE]* {}
Error: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/uamqp/src/saslclientio.c Func:saslclientio_close_async Line:1114 saslclientio_close called while not open
Error: Time:Fri Aug 18 17:15:22 2017 File:/home/user/workspaceMisc/azure-iot-sdk-c/uamqp/src/connection.c Func:connection_close Line:1339 xio_close failed
I also tried to remove the CarVIN from the model and comment the corresponding method which didn't help either.
As I see a "not implementd" in the error logs: Is it possible to used AMQP device twins already or will it be "completed" later?
Compiler/OS: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609

Related

Delaying module start till edgeHub fully initiates

I am trying to implement a python module (say, my-module) on arm32v7 Raspberry Pi-3 model. The module is based on resin/rpi-raspbian:stretch (azure-iothub-device-client==1.4.0b0). I have the iothub_client python library then working fine inside the module.
However when I am trying to deploy and do the iotedgectl start in the Pi, I get the following error in docker logs -f <my-module> :
Python 2.7.13 (default, Nov 24 2017, 17:33:09)
[GCC 6.3.0 20170516]
IoT Hub Client for Python
Adding TrustedCerts from: /mnt/edgemodule/edge-device-ca.cert.pem
set_option TrustedCerts successful
Converted audio file 2643035.wav in 5.67014288902 seconds
Payload: {"translatedutctime": "2018-06-23T14:56:59.972036", "filename": "2643035.wav"}
Sending Payload for 2643035.wav ...
Error: Time:Sat Jun 23 14:56:59 2018 File:/usr/sdk/src/c/c-utility/adapters/socketio_berkeley.c Func:socketio_open Line:701 Failure: connect failure 111.
Error: Time:Sat Jun 23 14:56:59 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:on_underlying_io_open_complete Line:751 Invalid tlsio_state. Expected state is TLSIO_STATE_OPENING_UNDERLYING_IO.
Error: Time:Sat Jun 23 14:56:59 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:tlsio_openssl_open Line:1251 Failed opening the underlying I/O.
Error: Time:Sat Jun 23 14:56:59 2018 File:/usr/sdk/src/c/umqtt/src/mqtt_client.c Func:mqtt_client_connect Line:980 Error: io_open failed
Error: Time:Sat Jun 23 14:56:59 2018 File:/usr/sdk/src/c/iothub_client/src/iothubtransport_mqtt_common.c Func:SendMqttConnectMsg Line:1932 failure connecting to address elderberrypi.
Error: Time:Sat Jun 23 14:57:00 2018 File:/usr/sdk/src/c/c-utility/adapters/socketio_berkeley.c Func:socketio_open Line:701 Failure: connect failure 111.
Error: Time:Sat Jun 23 14:57:00 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:on_underlying_io_open_complete Line:751 Invalid tlsio_state. Expected state is TLSIO_STATE_OPENING_UNDERLYING_IO.
Error: Time:Sat Jun 23 14:57:00 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:tlsio_openssl_open Line:1251 Failed opening the underlying I/O.
Error: Time:Sat Jun 23 14:57:00 2018 File:/usr/sdk/src/c/umqtt/src/mqtt_client.c Func:mqtt_client_connect Line:980 Error: io_open failed
Error: Time:Sat Jun 23 14:57:00 2018 File:/usr/sdk/src/c/iothub_client/src/iothubtransport_mqtt_common.c Func:SendMqttConnectMsg Line:1932 failure connecting to address elderberrypi.
Error: Time:Sat Jun 23 14:57:02 2018 File:/usr/sdk/src/c/c-utility/adapters/socketio_berkeley.c Func:socketio_open Line:701 Failure: connect failure 111.
Error: Time:Sat Jun 23 14:57:02 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:on_underlying_io_open_complete Line:751 Invalid tlsio_state. Expected state is TLSIO_STATE_OPENING_UNDERLYING_IO.
Error: Time:Sat Jun 23 14:57:02 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:tlsio_openssl_open Line:1251 Failed opening the underlying I/O.
Error: Time:Sat Jun 23 14:57:02 2018 File:/usr/sdk/src/c/umqtt/src/mqtt_client.c Func:mqtt_client_connect Line:980 Error: io_open failed
Error: Time:Sat Jun 23 14:57:02 2018 File:/usr/sdk/src/c/iothub_client/src/iothubtransport_mqtt_common.c Func:SendMqttConnectMsg Line:1932 failure connecting to address elderberrypi.
Converted audio file 4417734.wav in 4.16613197327 seconds
Payload: {"translatedutctime": "2018-06-23T14:57:04.059473", "filename": "4417734.wav"}
Sending Payload for 4417734.wav ...
Error: Time:Sat Jun 23 14:57:06 2018 File:/usr/sdk/src/c/c-utility/adapters/socketio_berkeley.c Func:socketio_open Line:701 Failure: connect failure 111.
Error: Time:Sat Jun 23 14:57:06 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:on_underlying_io_open_complete Line:751 Invalid tlsio_state. Expected state is TLSIO_STATE_OPENING_UNDERLYING_IO.
Error: Time:Sat Jun 23 14:57:06 2018 File:/usr/sdk/src/c/c-utility/src/tlsio_openssl.c Func:tlsio_openssl_open Line:1251 Failed opening the underlying I/O.
Error: Time:Sat Jun 23 14:57:06 2018 File:/usr/sdk/src/c/umqtt/src/mqtt_client.c Func:mqtt_client_connect Line:980 Error: io_open failed
Error: Time:Sat Jun 23 14:57:06 2018 File:/usr/sdk/src/c/iothub_client/src/iothubtransport_mqtt_common.c Func:SendMqttConnectMsg Line:1932 failure connecting to address elderberrypi.
Converted audio file 4486452.wav in 4.94396114349 seconds
Payload: {"translatedutctime": "2018-06-23T15:32:28.491401", "filename": "4486452.wav"}
Sending Payload for 4486452.wav ...
Confirmation[0] received for message with result = MESSAGE_TIMEOUT
Properties: {}
Total calls confirmed: 1
Now this goes on for several messages, and only after the start (never in between, once it stabilizes). After several such message timeouts and errors, the scenario returns back to normal, with callback confirmation, and I am also, able to receive the messages in IoTHub. As a result I always miss the first 5-10 messages and am unable to see those messages in IotHub.
After much trouble shooting, I figured there is a consistent problem. The edgeHub module always seems to fully initialize several seconds after my-module already start sending messages. Since edgeHub is not fully initialized and TLS authentication and MQTT paths are not set, the first few messages of my-module are lost. Maybe this is because the raspberry pi is a slow device?
I have tried starting my-module manually, after the edgeHub is fully initialized, all messages are delivered without any issues in that case.
Question: Is there a way to wait for the edgeHub to fully initialize and then start sending messages? More importantly, is this the actual problem or something else altogether is the cause of the issue?
Please let me know if more information is needed to get the problem context. I have tried to keep my query concise :)
What you pointed out is an accurate description of current behavior! As of current implementation, all modules are started at the same time. Some of them are initialized faster than edgeHub, which caused the behavior you'd seen. This is a known problem and we are implementing a fix!

Ad-hoc IPA not getting installed in ipod touch, stuck with installing message

I have been stuck with this weird problem for a while now. The Ad-hoc IPA is stuck with 'installing' message forever in ipod touch 5th gen.
Here is the console output at the time of installation :
Jul 17 18:13:38 Sreejiths-iPod installd[61] <Notice>: 0x387000 handle_install_for_ls: Install of "/var/mobile/Media/PublicStaging/Test.ipa" reTested by atc
Jul 17 18:13:38 Sreejiths-iPod atc[894] <Warning>: [VoiceMemosSyncClient][Orphan-Recovery] (post-sync, no new synced assets) checking for orphaned recordings.
Jul 17 18:13:38 Sreejiths-iPod installd[61] <Notice>: 0x387000 MobileInstallationInstall_Server: Installing app co.Testapp.Test
Jul 17 18:13:38 Sreejiths-iPod installd[61] <Error>: profile not valid: 0xe8008012
Jul 17 18:13:38 Sreejiths-iPod installd[61] <Error>: 0x387000 install_embedded_profile: Could not install embedded profile: 0xe8008012
Jul 17 18:13:38 Sreejiths-iPod atc[894] <Warning>: [VoiceMemosSyncClient][Orphan-Recovery] (post-sync, no new synced assets) done.
Jul 17 18:13:38 Sreejiths-iPod atc[894] <Warning>: [ML3MusicLibrary] compacting artwork
Jul 17 18:13:38 Sreejiths-iPod atc[894] <Warning>: [ML3MusicLibrary] removing 0 artwork cache ids no longer used
Jul 17 18:13:38 Sreejiths-iPod mobile_assertion_agent[121] <Notice>: service_one_connection: Connection closed for client iTunes.
Jul 17 18:13:38 Sreejiths-iPod medialibraryd[220] <Warning>: {MediaLibrary} [MLWriter] ending transaction <__NSConcreteUUID 0x16d692f0> 209F4AA6-959D-4FA9-BDA2-E39C052E40EB. shouldCommit=0.
Jul 17 18:13:39 Sreejiths-iPod installd[61] <Error>: 0x387000 verify_signer_identity: MISValidateSignatureAndCopyInfo failed for /var/tmp/install_staging.aAeAYo/foo_extracted/Payload/Test.app/Test: 0xe8008015
Jul 17 18:13:39 Sreejiths-iPod installd[61] <Error>: 0x387000 do_preflight_verification: Could not verify executable at /var/tmp/install_staging.aAeAYo/foo_extracted/Payload/Test.app
Jul 17 18:13:39 Sreejiths-iPod atc[894] <Error>: 0x1c0a000 MobileInstallationInstallForLaunchServices: failed with -1
Jul 17 18:13:39 Sreejiths-iPod installd[61] <Error>: 0x387000 install_application: Could not preflight application install
Jul 17 18:13:39 Sreejiths-iPod atc[894] <Warning>: ERROR: MobileInstallationInstallForLaunchServices returned nil
Jul 17 18:13:39 Sreejiths-iPod lsd[130] <Warning>: LaunchServices: installation failed for app co.Testapp.Test
Jul 17 18:13:39 Sreejiths-iPod atc[894] <Warning>: LaunchServices: installPhaseFinishedForProgress: co.Testapp.Test.Installing - <NSProgress: phase=Installing; state=Failed; fractionCompleted=0.000000> called, removing progress from cache
Jul 17 18:13:39 Sreejiths-iPod atc[894] <Warning>: {MediaLibrary} Database validation succeeded
Jul 17 18:13:39 Sreejiths-iPod installd[61] <Error>: 0x387000 handle_install_for_ls: API failed
Jul 17 18:13:39 Sreejiths-iPod medialibraryd[220] <Warning>: {MediaLibrary} [MLWriter] ending transaction <__NSConcreteUUID 0x16e833d0> 57B6C644-ED9D-4394-B2FF-B98B77107134. shouldCommit=0.
Is it related to Provisioning Profiles? I followed Somewhat-same-issue this post and checked the file as suggested but its still the same.
Has anyone else been facing this issue?
Any help will be much appreciated. Thanks.
So the problem was with the Device Profile.
I forgot to add my iPod Touch in the Device list.
Member Center > Certificates > Devices > Add new device . Voila. Everything started working.

Error on startup for mongodb server

totally new to mongodb. I'm trying to install locomotive CMS on my server, which is cool, but I've always used SQL/MySQL so mongo is totally new to me.
I installed all the needed mongodb modules, but when I run: sudo service mongod start I get an error code. When I look in the logs for the error, here is what is output:
Fri Mar 21 18:13:47.186 [initandlisten] MongoDB starting : pid=5053 port=27017 dbpath=/var/lib/mongo 64-bit host=vagrant-centos64.vagrantup.com
Fri Mar 21 18:13:47.186 [initandlisten] db version v2.4.9
Fri Mar 21 18:13:47.186 [initandlisten] git version: 52fe0d21959e32a5bdbecdc62057db386e4e029c
Fri Mar 21 18:13:47.186 [initandlisten] build info: Linux ip-10-2-29-40 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_49
Fri Mar 21 18:13:47.186 [initandlisten] allocator: tcmalloc
Fri Mar 21 18:13:47.186 [initandlisten] options: { config: "/etc/mongod.conf", dbpath: "/var/lib/mongo", fork: "true", logappend: "true", logpath: "/var/log/mongo/mongod.log", pidfilepath: "/var/run/mo$
Fri Mar 21 18:13:47.192 [initandlisten] journal dir=/var/lib/mongo/journal
Fri Mar 21 18:13:47.192 [initandlisten] recover : no journal files present, no recovery needed
Fri Mar 21 18:13:47.192 [initandlisten]
Fri Mar 21 18:13:47.192 [initandlisten] ERROR: Insufficient free space for journal files
Fri Mar 21 18:13:47.192 [initandlisten] Please make at least 3379MB available in /var/lib/mongo/journal or use --smallfiles
Fri Mar 21 18:13:47.192 [initandlisten]
Fri Mar 21 18:13:47.193 [initandlisten] exception in initAndListen: 15926 Insufficient free space for journals, terminating
Fri Mar 21 18:13:47.193 dbexit:
Fri Mar 21 18:13:47.193 [initandlisten] shutdown: going to close listening sockets...
Fri Mar 21 18:13:47.193 [initandlisten] shutdown: going to flush diaglog...
Fri Mar 21 18:13:47.193 [initandlisten] shutdown: going to close sockets...
Fri Mar 21 18:13:47.193 [initandlisten] shutdown: waiting for fs preallocator...
Fri Mar 21 18:13:47.193 [initandlisten] shutdown: lock for final commit...
Fri Mar 21 18:13:47.193 [initandlisten] shutdown: final commit...
Fri Mar 21 18:13:47.193 [initandlisten] shutdown: closing all files...
Fri Mar 21 18:13:47.193 [initandlisten] closeAllFiles() finished
Fri Mar 21 18:13:47.193 [initandlisten] journalCleanup...
Fri Mar 21 18:13:47.193 [initandlisten] removeJournalFiles
Fri Mar 21 18:13:47.193 [initandlisten] shutdown: removing fs lock...
Fri Mar 21 18:13:47.193 dbexit: really exiting now
Also, I run: sudo service mongod status and the output is mongod is stopped so I know it's not running.
Following the stack, it looks like the error has something to do with insufficient space, but my server has 15gb free and im running sudo, so i know it's not a permission error....how can I allocate more space...or better yet, what should i allocate more space to?
Any help is appreciated.
Add smallfiles = true to "/etc/mongodb.conf".
Now try to start the service, I assume this should fix the issue!!
Set to true to modify MongoDB to use a smaller default data file size. Specifically, smallfiles reduces the initial size for data files and limits them to 512 megabytes. The smallfiles setting also reduces the size of each journal files from 1 gigabyte to 128 megabytes.

my app is getting crash while running on device

my app is working fine on simulator but when i am running on device its getting crash and showing these reports
Aug 11 15:02:04 unknown MobileMail[20218] : Received memory warning.
Aug 11 15:02:04 unknown UserEventAgent[12] : jetsam: kernel termination snapshot being created
Aug 11 15:02:04 unknown com.apple.launchd[1] : (UIKitApplication:com.apple.mobilephone[0xc8a9]) Exited: Killed: 9
Aug 11 15:02:04 unknown com.apple.launchd[1] : (UIKitApplication:com.apple.mobilemail[0x828b]) Exited: Killed: 9
Aug 11 15:02:04 unknown com.apple.launchd[1] : (UIKitApplication:com.christopher.pacificamodeling[0x8500]) Exited: Killed: 9
Aug 11 15:02:04 unknown com.apple.launchd[1] : (UIKitApplication:com.skype.skype[0xd976]) Exited: Killed: 9
Aug 11 15:02:05 unknown SpringBoard[16688] : Application 'Mail' exited abnormally with signal 9: Killed: 9
Aug 11 15:02:05 unknown SpringBoard[16688] : Application 'PacifiCA' exited abnormally with signal 9: Killed: 9
Aug 11 15:02:06 unknown SpringBoard[16688] : Application 'Skype' exited abnormally with signal 9: Killed: 9
Aug 11 15:02:06 unknown SpringBoard[16688] : Application 'Phone' exited abnormally with signal 9: Killed: 9
Aug 11 15:02:06 unknown DTPower[15342] : Task info failed for task com.christopher.pacificamodeling
Aug 11 15:02:06 unknown kernel[0] : launchd[20223] Builtin profile: MobileMail (sandbox)
Aug 11 15:02:06 unknown kernel[0] : launchd[20224] Builtin profile: container (sandbox)
Aug 11 15:02:06 unknown kernel[0] : launchd[20224] Container: /private/var/mobile/Applications/6BBDF6EB-1DB0-4CAB-8300-DC6CBA78C1AB [69] (sandbox)
First thing is to run the profiler from xcode menu as shown below:
then use the one highlighted below:
Finally you will see the blocks that is allocated the most expand any of them to see who is allocating it frequently. Go to that part and optimize it to avoid allocate/deallocate every time.

XCode 4 Crash but not sure why?

XCode4 just crash on me when I was testing my app without saying why. I put the crash log I found on the device below. The app runs fine in the simulation so I am thinking it's the memory problem? I check for leaks but there is nothing serious to it, also there is not memory warning call.
The log said "Saved crashreport to /Library/Logs/CrashReporter/LowMemory-2011-06-01-154632.plist" but I can't find it anywhere on my mac.
Please help,
Pondd
Jun 1 15:46:31 unknown com.apple.launchd[1] <Notice>: (UIKitApplication:com.mondial.dva[0xd591]) Bug: launchd_core_logic.c:3795 (24506):0
Jun 1 15:46:31 unknown com.apple.launchd[1] <Notice>: (UIKitApplication:com.mondial.dva[0xd591]) Bug: launchd_core_logic.c:920 (24506):3
Jun 1 15:46:31 unknown com.apple.debugserver-50[412] <Warning>: 1 [019c/1503]: error: ::read ( 4, 0x2ff8a9f0, 1024 ) => -1 err = Bad file descriptor (0x00000009)
Jun 1 15:46:31 unknown com.apple.launchd[1] <Notice>: (UIKitApplication:com.mondial.dva[0xd591]) Bug: launchd_core_logic.c:3794 (24506):3
Jun 1 15:46:31 unknown com.apple.launchd[1] <Notice>: (UIKitApplication:com.mondial.dva[0xd591]) Bug: launchd_core_logic.c:3202 (24506):10
Jun 1 15:46:31 unknown com.apple.launchd[1] <Notice>: (UIKitApplication:com.mondial.dva[0xd591]) Working around 5020256. Assuming the job crashed.
Jun 1 15:46:31 unknown SpringBoard[28] <Warning>: Unable to delete job with label UIKitApplication:com.mondial.dva[0xd591]. Error: No such process
Jun 1 15:46:32 unknown ReportCrash[418] <Error>: Saved crashreport to /Library/Logs/CrashReporter/LowMemory-2011-06-01-154632.plist using uid: 0 gid: 0, synthetic_euid: 0 egid: 0
Jun 1 15:46:32 unknown configd[25] <Notice>: jetsam: kernel termination snapshot being created
Jun 1 15:46:32 unknown SCHelper[148] <Notice>: active (but IDLE) sessions
Jun 1 15:46:37 unknown SpringBoard[28] <Notice>: MultitouchHID(1cd11840) uilock state: 0 -> 1
Jun 1 15:46:41 unknown ReportCrash[420] <Notice>: Not saving Jetsam log because no data from the kernel.
Jun 1 15:46:41 unknown configd[25] <Notice>: jetsam: kernel termination snapshot being created
Jun 1 15:46:51 unknown ReportCrash[421] <Notice>: Not saving Jetsam log because no data from the kernel.
I found my LowMemory generated files through the organizer -> devices -> the device you are running on -> console -> right click on any of the logs on the left and select "Reveal in Finder"