Jump to content

spants

Community Developer
  • Posts

    637
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by spants

  1. Working here with beta20 and a TBS card. Good job  :D

     

    In case there are someone else with a TBS card and a Supermicro X9 motherboard I experienced some troubles getting the TBS card recognized (6985). It did not show in the device list in unraid.

    After a little bit of googling I found the solution to be to set the speed of the PCIe port to GEN1. Some might also have to set the below for tit to work.

     

    Active state power management = ForceLOs

     

    After this I had no problem getting the card to work. Don't really know if it works as I don't have a dish anymore, but it's found by Tvheadend  :)

     

    Here is the link for the above info in case someone wants some more reading.

     

    http://www.tbsdtv.com/forum/viewtopic.php?f=52&t=7712#p25154

     

    Thanks! I had the same problem with an ASUS mb. AUTO disables the slot it was in but GEN1 makes it work

  2. I have updated the NodeRed docker to allow the easy updating of the Nodes to the latest versions without me updating the Docker. To do this, I removed them from the build - you can reinstall them in the Admin tab (top right). Your flows will need you to re add the missing nodes that are used.

     

    The affected Nodes are:

    node-red-contrib-ibmpush

    node-red-contrib-googlechart

    node-red-contrib-nest

    node-red-contrib-splitter

    json-db-node-red

    node-red-contrib-freeboard

    node-red-contrib-sunevents

    node-red-node-badwords

    node-red-node-exif

    node-red-node-geofence

    node-red-node-mysql

    node-red-node-ping

    node-red-node-wol

    node-red-node-web-nodes

    node-red-node-base64

    node-red-node-geohash

    node-red-node-twilio

    node-red-node-pushbullet

    node-red-node-aws

    node-red-contrib-ibm-watson-iot

    node-red-contrib-timeseries

    node-red-node-emoncms

    node-red-contrib-hue

    node-red-contrib-blynk

    node-red-contrib-pebble-watch

    node-red-node-twitter

    node-red-contrib-graphs

    node-red-contrib-influxdb

    node-red-contrib-bigtimer

    node-red-contrib-firebase

    node-red-contrib-ui

    node-red-contrib-admin

    node-red-node-smooth

    node-red-contrib-scx-ibmiotapp

    node-red-contrib-json

    node-red-contrib-eibd

  3. I've just totally rebuilt the MQTT docker to use Alpine Linux 3.3 - which is the version of Linux favoured by the Docker team.

     

    I have removed all the fancy Nobody/User settings as the have caused problems to me when I wanted to use the same docker on my mac.

     

    The issue will be is that to edit the settings on first use - defaults are created - you may need to run a NEWPERMS on the data directory.

     

    If you already have run the older version, it can use the settings but there is an updated EXAMPLE file that might be a better base: it shows the connects in the log window but doesnt create a huge logfile.

     

    For non mnt/user/ this may work better for you.

     

    *** Please let me know if it works or breaks something!!! ***

     

    (Note: that you will need the 1st May version - not the April)

  4. I tried the new one, same error as the old docker unfortunately. Tried experimenting a little bit more, what I found is that if I invoke the docker at the command line with different PGID and PUID I can read the config file fine, however it then complains that it can't find user mosquitto. Don't know if that helps with troubleshoting at all.

     

     

    Yes, thanks!

    I think that it is because you are using the /mnt/ and not /mnt/user/ hierarchy ..... I tested with the data on the protected raid and not on a cache drive. I will try and look at this over the weekend.

     

    Can I check that you really want to have your data stored in this way?. If you create a share that is only on one disk then it is that disk and parity that will be spinning. There is not a lot of energy difference and the strain on a disk is when it is starting up.

  5. I have been using and writing a lot of Docker images and thought that I would take a look at VMs. However, none will start:

     

    LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'Windows 7' -S -machine pc-i440fx-2.5,accel=kvm,usb=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -m 2048 -realtime mlock=off -smp 2,sockets=1,cores=1,threads=2 -uuid e8e3ee70-eaa9-e1cd-68e6-14c24d766113 -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Windows 7/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive 'file=/mnt/cache/.keep/vm/Windows 7/v-device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on
    Domain id=2 is tainted: high-privileges
    Domain id=2 is tainted: host-cpu
    char device redirected to /dev/pts/0 (label charserial0)
    

     

    I have tried selecting other CPU cores etc.

     

    This seems to be the problem:

    Domain id=2 is tainted: high-privileges
    Domain id=2 is tainted: host-cpu

     

    argggg: I guess I need IOMMU capability?. No menu to set it...

     

    Model: N/A

    M/B: ASUSTeK Computer INC. - P8Z68-V PRO

    CPU: Intel® Core™ i7-2600K CPU @ 3.40GHz

    HVM: Enabled

    IOMMU: Disabled

    Cache: 256 kB, 1024 kB, 8192 kB

    Memory: 16384 MB (max. installable capacity 32 GB)

    Network: eth0: 1000Mb/s, Full Duplex, mtu 1500

    Kernel: Linux 4.4.6-unRAID x86_64

    OpenSSL: 1.0.2g

    Uptime:

  6. the mqtt client seems borked - it doesn't work with external mqtt server either.

     

     

    Traceback (most recent call last):

    File "/usr/local/lib/python3.4/threading.py", line 911, in _bootstrap_inner

    self.run()

    File "/usr/local/lib/python3.4/threading.py", line 859, in run

    self._target(*self._args, **self._kwargs)

    File "/usr/local/lib/python3.4/site-packages/paho/mqtt/client.py", line 2287, in _thread_main

    self.loop_forever()

    File "/usr/local/lib/python3.4/site-packages/paho/mqtt/client.py", line 1261, in loop_forever

    rc = self.loop(timeout, max_packets)

    File "/usr/local/lib/python3.4/site-packages/paho/mqtt/client.py", line 811, in loop

    rc = self.loop_read(max_packets)

    File "/usr/local/lib/python3.4/site-packages/paho/mqtt/client.py", line 1073, in loop_read

    rc = self._packet_read()

    File "/usr/local/lib/python3.4/site-packages/paho/mqtt/client.py", line 1475, in _packet_read

    rc = self._packet_handle()

    File "/usr/local/lib/python3.4/site-packages/paho/mqtt/client.py", line 1943, in _packet_handle

    return self._handle_publish()

    File "/usr/local/lib/python3.4/site-packages/paho/mqtt/client.py", line 2095, in _handle_publish

    (message.topic, packet) = struct.unpack(pack_format, packet)

    struct.error: bad char in struct format

     

  7. You can add the node-red-node-pushover node via the admin tab and it should persist between updates......

     

    edit the node-red-contrib by using backspace.

     

    (is this how you are doing it?.... make sure that you are also pointing /data to a directory on your drives - in my case /mnt/user/docker/appdata/nodered so that the flows and additions persist)

  8. K, thanks for trying that. Personally I would create a docker appdata directory and store the files on the protected disks. I would hate to lose the configs for my 17 dockers!.

     

    The downside is that one disk stays spinning... the wear and tear is not much (better than sleeping/restarting) but it uses a slight amount of energy.

     

    I will try and nail this issue down a bit but I have a busy weekend coming up!.

    I wonder if the linuxserver.io sonar/plex have this issue... will try

     

    (btw - the client error that you have, does the client have an id and have you disabled anon in the config fiel if you are not using a password)

  9. I agree - it looks like permissions. Have you tried stopping mqtt and doing a newperms on that mqtt data folder?

     

    Are you using the linuxserver.io versions of those dockers? My mqtt is based on linuxserver/baseimage so it should behave the same way.

     

    If you have your docker data share on one disk, only that one will spin up but your data is protected if you have a disk fault.

×
×
  • Create New...