Announcement

Collapse
No announcement yet.

HSBuddy causes system crash twice

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    HSBuddy causes system crash twice

    This morning HSBuddy causes a system crash. At 04:30:49 there was the last correct message from HSBuddy. Three minutes later errors start beeing generated and the last 2 messages (these from 04:42:44 and 04:43:43) were repeated massively until 07:37:10 and then the system crashed.

    2021-06-09 04:43:43 Error Saving database: Conversion from string "Insufficient memory to continue the execution of the program." to type 'Integer' is not valid.
    2021-06-09 04:42:44 HSBuddy Error processing a device change. System.Exception: Timeout occured. Did not receive a response. at HSCF.Communication.ScsServices.Communication.RequestReplyMes senger`1[T].SendMessageAndWaitForResponse (HSCF.Communication.Scs.Communication.Messages.IScsMessage message,​ System.Int32 timeoutMilliseconds) [0x00079] in :0 at HSCF.Communication.ScsServices.Communication.RequestReplyMes senger`1[T].SendMessageAndWaitForResponse (HSCF.Communication.Scs.Communication.Messages.IScsMessage message) [0x00008] in :0 at HSCF.Communication.ScsServices.Communication.RemoteInvokePro xy`2[TProxy,​TMessenger].Invoke (System.Runtime.Remoting.Messaging.IMessage msg) [0x00056] in :0 at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (System.Runtime.Remoting.Proxies.RealProxy rp,​ System.Runtime.Remoting.Messaging.IMessage msg,​ System.Exception& exc,​ System.Object[]& out_args) [0x000d6] in <533173d24dae460899d2b10975534bb0>:0 at (wrapper managed-to-native) System.Object.__icall_wrapper_mono_remoting_wrapper(intptr,​ intptr) at (wrapper remoting-invoke) HomeSeerAPI.IHSApplication.GetDeviceByRef(int) at HSPI_HSBuddy.Native.HomeSeer.GetDeviceByRef (System.Int32 dvRef) [0x00000] in <7a28d045d8954a5f95123eb236685da8>:0 at HSPI_HSBuddy.Devices.DeviceManager.ConsumeOperation (HSPI_HSBuddy.Devices.DeviceManager+DeviceOperation operation) [0x00051] in <7a28d045d8954a5f95123eb236685da8>:0 at HSPI_HSBuddy.Devices.DeviceManager.ConsumeOperations () [0x00023] in <7a28d045d8954a5f95123eb236685da8>:0
    2021-06-09 04:42:43 Error Saving database: Conversion from string "Insufficient memory to continue the execution of the program." to type 'Integer' is not valid.
    2021-06-09 04:41:43 Error Saving database: Conversion from string "Insufficient memory to continue the execution of the program." to type 'Integer' is not valid.
    2021-06-09 04:40:42 Error Error while serializing object for database : Insufficient memory to continue the execution of the program.
    2021-06-09 04:34:23 Error Error while serializing object for database : Insufficient memory to continue the execution of the program.
    2021-06-09 04:33:22 Error Error while serializing object for database : Insufficient memory to continue the execution of the program.
    2021-06-09 04:30:49 HSBuddy Cleanup thread removed 4496 entries from device history.
    The system rebooted and at about 07:40 I removed the database hsbuddy.db3 and rebooted the HS4 system again. The database had a size of about 50 MB.

    Then, at 07:59:29 I got this message in the log:
    2021-06-09 07:59:29 HSBuddy Error processing a device history event. SQLite.SQLiteException: ReadOnly at SQLite.PreparedSqlLiteInsertCommand.ExecuteNonQuery (System.Object[] source) [0x00134] in :0 at SQLite.SQLiteConnection.Insert (System.Object obj,​ System.String extra,​ System.Type objType) [0x000f4] in :0 at SQLite.SQLiteConnection.Insert (System.Object obj) [0x00012] in :0 at HSPI_HSBuddy.History.DeviceHistory.ConsumeChange (HSPI_HSBuddy.Data.DeviceChange change) [0x0001c] in <7a28d045d8954a5f95123eb236685da8>:0 at HSPI_HSBuddy.History.DeviceHistory.ConsumeChanges () [0x0001d] in <7a28d045d8954a5f95123eb236685da8>:0
    These mesages arrived massively until 08:00:46 and then I rebooted the system again. Up till now (11:31) everything is OK. The database has a size of about 4MB and I could successfully upload the dashboards.

    I am running HS4 version 4.1.16.0 on a Raspberry Pi4 with 4GB of memory. The OS is the PiOS.

    This is my profile:

    Date/time=9-6-2021 11:27:28 CEST
    Version=HS4 Standard Edition 4.1.16.0 (Linux)
    MONO Version=Mono JIT compiler version 6.12.0.122 (tarball Mon Feb 22 17:44:05 UTC 2021)

    License=Registered
    License ID=XXXXX
    MyHS Subscription=Basic
    MyHS Subscription Backup Interval=No Backup
    MyHS Subscription Max Cameras=1
    Confguration File=/usr/local/HomeSeer/Data/HomeSeerData.json
    Uptime=0 Days 3 Hours 23 Minutes 48 Seconds
    User/Access=Cor (Admin)
    Lan IP=192.168.1.20 (RPi4-HS4)
    Client IP=192.168.1.157 (192.168.1.157)
    WAN IP=XXXXXXXXXXXXX
    Device Count=538
    Event Count=277
    Last Event Ran=Rapporten : Update CPU load, Ran at 9-6-2021 11:26:00
    # of unique event scripts=17
    Plugins Enabled=UltraLog3:,Tuya:,Z-Wave:,Pushover 3P:,Device History:,CM15A:,DoorBird:,HSBuddy:,mcsMQTT:
    Modules/Threads=92 Modules, 93 Threads
    Available Threads=399
    HomeSeer Memory Used=172 Mbytes
    Plugins Installed=CM15A 3.0.0.7,Device History 3.1.4.1,DoorBird 0.0.0.31,HSBuddy 3.24.326.10,mcsMQTT 5.16.0.5,Pushover 3P 0.0.0.52,Tuya 4.0.27.0,UltraLog3 3.0.6644.26753,Z-Wave 3.0.2.1

    Has anybodcy a clue of what happened. Was it really a memory problem?

    -- Cor --
    Tags: None
Previous template Next
Working...
X