Announcement

Collapse
No announcement yet.

Mono release 5.20.1 Stable (5.20.1.19). On ubuntu server x64

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mono release 5.20.1 Stable (5.20.1.19). On ubuntu server x64

    This is weird.

    here are my steps:

    1- turn of hs3 via systemctl stop hs3
    2 apt update && apt upgrade -y
    3 Turn on hse 3 service : systemctl start hs3
    -All the plugins loads fine.
    4-reboot my pc .
    5-None of the plugins load ( plugin is pending )
    6- repeat step 1 and 3. The plugins loads fine.
    7- Reboot the pc. plugins load fine.

    Maybe the is some sort of caching introduced in this release?


    -----

    Next release risk to be 6.1.x.x wonder if it will be a big change :O


  • #2
    Just noticied , that the zwave plugin is going crazy right now, and it seems to stay there.

    Running z-wave beta v.261


    edit: restarting the plugin do not help.
    Runing z wave v252 does not help too.
    Attached Files

    Comment


    • #3
      WIll remove mono from my system and reinstall the last install i had, and try to lock it!

      After another pc restart, same problem as in the begining....no plugin starts

      Comment


      • #4
        If anyone want to lock mono this is what you need on Ubuntu x64 into the ppa file.

        deb https://download.mono-project.com/repo/ubuntu bionic/snapshots/5.18.1.3 main

        Comment


        • #5
          ...returned to 5.18.1.0.

          th z wave issue is still there ? I really do not understand this. Maybe something got corrupted in the process?


          Edit : Turning the PC completely off . unpluging the z wave stick. Plugged it back... Restarting the pc.

          This solved the z wave issue.
          -----

          Will not update to 5.20.x.x there is definitely an issue with plugins not loading .
          Will let someone else try and report back


          edit: here is my setup if that could in some way help to find plugin load issue ( if i am not alone).

          Code:
          Current Date/Time: 2019-04-11 8:46:15 PM
          HomeSeer Version: HS3 Pro Edition 3.0.0.531
          Linux version: Linux Automation 5.0.7-050007-generic #201904052141 SMP Fri Apr 5 21:43:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux System Uptime: 0 Days 1 Hour 19 Minutes 10 Seconds
          IP Address: 192.168.x.x
          Number of Devices: 686
          Number of Events: 345
          Available Threads: 1599
          HSTouch Enabled: False
          Event Threads: 18
          Event Trigger Eval Queue: 0
          Event Trigger Priority Eval Queue: 0
          Device Exec Queue: 0
          HSTouch Event Queue: 0
          Email Send Queue: 0
          
          Enabled Plug-Ins
          3.0.0.13: AirplaySpeak
          3.3.2.1: APCUPSD
          1.28.0.0: Big5
          1.3.7.3: Device History
          3.0.0.64: EasyTrigger
          2.0.3.2: JowiHue
          3.0.1.14: Kodi
          3.0.0.118: LutronCaseta
          3.1.0.17: MeiHarmonyHub
          3.0.0.63: PHLocation2
          0.0.0.46: Pushover 3P
          3.2.0.6: SqueezeBox
          3.0.6644.26753: UltraLog3
          3.0.1.261: Z-Wave

          Comment


          • #6
            I am currently running HS3 V.431 and kept Mono at V.5.18.1.0 running on Armbian Ubuntu 18.04 64 bit. ZWave is via a ZNet like RPi POE connected in the attic.

            Only update done here was for HS3. I have not had any issues with ZWave.

            - Pete

            Auto mator
            Homeseer 3 Pro - 3.0.0.500 (Linux) - Ubuntu 18.04 64 bit Intel CPU - Mono 5.18
            Homeseer Zee2 (Lite) - 3.0.0.531 (Linux) - ARMBian Ubuntu 18.04 64 bit Arm CPU - Mono 5.20

            X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

            Comment


            • #7
              Resolved the z wave issue ( see post #5).

              Maybe another one could xplain us, why a complete poweroff of the system did work? Maybe some sort a bad RAM purge with the restart... or on the stick memory itself?

              Comment


              • #8
                Just wanted to report that the latest version of mono for raspberry pi / stretch is working so far with homeseer 3 and aspx scripts if you apply the vbnc patch. I did power cycle the Pi before checking.

                Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:28:30 UTC 2019)
                Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
                TLS: __thread
                SIGSEGV: normal
                Notifications: epoll
                Architecture: armel,vfp+hard
                Disabled: none
                Misc: softdebug
                Interpreter: yes
                LLVM: yes(600)
                Suspend: preemptive
                GC: sgen (concurrent by default)

                pi@raspberrypi:/usr/bin $ cat vbnc
                Code:
                #!/bin/bash
                for x; do
                if [[ $x = '/tmp'* ]]; then
                sed -i '1{/#Externa/d}' $x
                fi
                done
                exec /usr/bin/mono --debug $MONO_OPTIONS /usr/lib/mono/4.5/vbnc.exe "$@"

                Comment


                • #9
                  just updated to mono 5.20.1.19 and HS3 .531

                  everything running fine no hicups.
                  HS3 SEL running Pro Edition 3.0.0.531 on Ubuntu 18.04, mono 5.20, 656 devices, 209 events.
                  Plug-Ins: Chromecast, Device History, EasyTrigger, Ecobee, JowiHue, LutronCaseta, MeiUnifi, PHLocation2, Pushover 3P, SDJ-Health, Sonos, WeatherFlow, weatherXML
                  Scripts: SparkMan's Lock Event, 5 of Jon00 scripts.

                  Comment


                  • #10
                    On a pi/zee ? Or x86?

                    I might try it again after cloning my ssd.

                    This time I will reboot the server after the mono upgrade

                    Comment


                    • #11
                      On a Homeseer Sel running Ubuntu 18.04


                      Sent from my SM-G975U1 using Tapatalk

                      HS3 SEL running Pro Edition 3.0.0.531 on Ubuntu 18.04, mono 5.20, 656 devices, 209 events.
                      Plug-Ins: Chromecast, Device History, EasyTrigger, Ecobee, JowiHue, LutronCaseta, MeiUnifi, PHLocation2, Pushover 3P, SDJ-Health, Sonos, WeatherFlow, weatherXML
                      Scripts: SparkMan's Lock Event, 5 of Jon00 scripts.

                      Comment


                      • #12
                        Thanks

                        Comment


                        • #13
                          Here running Ubuntu 18.04 on an Intel and and an AMD CPU have no issues with the HS3 test aspx pages / Mono current release.

                          HS3Pro:~# mono -V
                          Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 09:02:17 UTC 2019)
                          Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
                          TLS: __thread
                          SIGSEGV: altstack
                          Notifications: epoll
                          Architecture: amd64
                          Disabled: none
                          Misc: softdebug
                          Interpreter: yes
                          LLVM: yes(600)
                          Suspend: hybrid
                          GC: sgen (concurrent by default)

                          Only on the quad core and octocore ARM CPU running Armbian Ubuntu 18.04 (arm64 or aarch64) do I have issues running aspx pages with current release of mono.

                          Pine64:~# mono -V
                          Mono JIT compiler version 5.20.1.19 (tarball Thu Apr 11 08:59:52 UTC 2019)
                          Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
                          TLS: __thread
                          SIGSEGV: normal
                          Notifications: epoll
                          Architecture: arm64
                          Disabled: none
                          Misc: softdebug
                          Interpreter: yes
                          LLVM: yes(600)
                          Suspend: preemptive
                          GC: sgen (concurrent by default)

                          In the process of moving HS3 Lite over to an Octocore ARM running Ubuntu 18.04 which will not fix the mono ASPX issue. Also changing it from using a microSD (fast) to eMMC.
                          - Pete

                          Auto mator
                          Homeseer 3 Pro - 3.0.0.500 (Linux) - Ubuntu 18.04 64 bit Intel CPU - Mono 5.18
                          Homeseer Zee2 (Lite) - 3.0.0.531 (Linux) - ARMBian Ubuntu 18.04 64 bit Arm CPU - Mono 5.20

                          X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

                          Comment


                          • #14
                            I have upgraded mono to V.5.20.

                            restarted 4 times to be sure all the plugins were starting...no issues.

                            But i saw...I had the same problem with the z wave plugin going to 200% cpu usage.

                            I turned off the z wave plugin...removed the z wave stick . Put it back . Started the z wave plugin again.

                            All went back to normal...


                            rebooted 3 times . Still ok.

                            not sure what the problem is/ was

                            Comment


                            • #15
                              After near 15 reboot of the server. no issues with plugins , and no issues with zwave plugin going 200%

                              Hope it be like that indefinitely

                              Comment

                              Working...
                              X