Error: no matches for OriginalId certmanager.k8s.io_v1alpha1_ClusterIssuer|~X|letsencrypt-staging

After spending the weekend fighting with the original Arcus code with error after error, I settled down and decided to use this script. After all, I merely just need to get the Iris functionality back which I can then hopefully incorporate into home assistant. However running the setup-local.sh, I get this error and it fails. I'm sure I can figure it out over time but am tired. Wondering if anyone else has seen this error and knows how to get past it.
Error: no matches for OriginalId certmanager.k8s.io_v1alpha1_ClusterIssuer|~X|letsencrypt-staging; no matches for CurrentId certmanager.k8s.io_v1alpha1_ClusterIssuer|~X|letsencrypt-staging; failed to find unique target for patch certmanager.k8s.io_v1alpha1_ClusterIssuer|letsencrypt-staging error: no objects passed to apply

I'm not familiar with that error, but I'm guessing that version 0.7 of cert-manager no longer works, and we will probably need to upgrade to a newer version. You could try changing the file that gets included as part of setup-local.sh
What functionality in Arcus are you hoping to incorporate into Home Assistant? Right now there's not a good way to expose functionality from Arcus to other platforms (but that's something I've been working on).

Tried using 0.8.1 but it still does it. I know it throws an error right before it
Error from server (AlreadyExists): secrets "shared" already exists
namespace/default labeled

Don't know if that has anything to do with it. As of right now, I have a Iris Thermostat and Alarm keypads, I'd like to get operational. I was good coding C in my day, but this is a learning curve I can tackle. If I could just get it installed.

That error isn't a problem - basically the setup script tries to create a secret based on the contents of "secret/" each time you run it - although kubernetes doesn't support/use secrets that way, and instead treats them as immutable (the opposite of configmaps, yay). If you make changes to your secrets you'll need to delete and recreate them, but otherwise it's fine to ignore this error.

function apply {
  ./kustomize build overlays/local-production-local/ | $KUBECTL apply -f -
}
retry 10 apply

Mind if I can get clarification on what this is doing? It's where the error is originating from.

That block of code runs kustomize (a tool to template/override kubernetes templates) and applies the configuration. If it fails, it will attempt up to 10 times (see the definition of retry in the scripts). If you're having a problem, it's not likely with this block of code, but rather in the configuration itself (e.g. in config/ or overlays/)

Also, it looks like there's a new problem with istio in microk8s due to microk8s being updated recently, see https://github.com/ubuntu/microk8s/issues/545

Not sure, I've tried installing microk8s using what was listed there, still same problem. I have noticed a problem with Istio. Kinda aggrevating really. In order to restart the installation, I have to uninstall microk8s to get it to not error out when it gets to Istio. microk8s.reset just hangs. I'll take another look at config. the overlays just populates the answers to the questions the script asks me. Unless I'm putting invalid info in it.

Yeah, it seems that istio/microk8s is generally broken for new installations. I thought the edge version of microk8s would work, but I guess not - I wonder if it's possible to install an older version of the snap that doesn't have these problems?
Also yes - microk8s.reset not working is something I've ran into as well. If you have specific errors you're seeing when applying the overlay, I'd be happy to take a look at those. Otherwise, I don't have a good solution to the overall kubernetes ecosystem maturity issues I believe we're running into other than I might consider dumping kubernetes overall in favor of k3s or even just docker compose.

The specific error I was getting was trying to override my admin email on the place holder. To save myself some headache, I decided to just hard code it and remove the overlay for that part. Got me a little farther, but not much.
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "clusterissuers.admission.certmanager.k8s.io": the server is currently unable to handle the request
Found this installed so not sure.
customresourcedefinition.apiextensions.k8s.io/clusterissuers.certmanager.k8s.io created
Going to try and use the default microk8s again and see what happens

I believe I've run into that error a few times - it takes a while for cert-manager to become available so you just have to kind of wait for it to play out. The script will attempt to apply the configuration multiple times until cert-manager is ready.

I have been watching this repo for a while... Is it usable/stable yet or still trying to get it to work correctly ?

Or count to 10 and time out :-P
If that's the case, I can try to increase the number of times to see if it's needing the extra time.

@sgrayban well, I've been using it for the last few months to run two Arcus environments, with several people on them, but I'm not aware of anyone other than me being able to get it running, which is unfortunate. Perhaps we should setup up some support channel or easier means of communication and work it out? There are some new people working on arcusplatform/arcusweb now, I might see if they can take some time and provide feedback, since we can iterate quicker that way.

Try #12, it got past it. Now gotta get past this hurdle.
Error from server (NotFound): pods "cassandra-0" not found
Progress. Making progress.

@AndrewX192 what are you running it on ?

@Kouruu looks good! Notification service can't start unless you have APNS credentials + paid apple developed account (sorry about that), and hub-bridge won't start until you run ./setup-hubkeystore.sh. Make sure you can get into the Arcus UI with a valid production certificate before you setup the hub trust store though.. otherwise the Hub won't be able to connect.
@sgrayban I'm running all my Arcus instances using the scripts provided in this repo (without any substantial modifications) inside of Ubuntu 18.04 virtual machines.

@AndrewX192 Does it really take all of this to run ? 12GB or more of RAM, and 15GB of disk space

It is what it is. If I don't need it for what I'm working on, I'm not really worried about it. Just trying to unbrick at least the useful Iris devices in the house and integrate them into a new setup.

@sgrayban my production instance is using 9GB of ram and a good 25GB of disk space. The drivers service in particular is very heavy on memory usage (almost 1GB) and kubernetes in general is not light on resources - although replacing it with k3s may help. You may be able to get it to run with less resources with some additional time invested, but I stopped at 8GB. Disk space usage depends on how busy your system is, and whether you decide to add system monitoring (the timeseries database will create tens of gigabytes in metrics).
@Kouruu it's entirely possible that having it run longer could have fixed it - I can imagine it may take longer for cert-manager to start on some systems. BTW if you're looking to port devices over, I'd recommend just looking at the device drivers in platform/arcus-containers/driver-services/src/main/resources and port them to your system of choice. The device model is very similar to that of SmartThings and Hubitat, so it shouldn't be very difficult to port - I've been using that to my advantage to add support for a bunch of new sensors in Arcus.

@AndrewX192 so it sounds like not really cost effective for personal use....

@sgrayban Arcus isn't for everyone, especially today. If you want something that runs on minimal resources, then you have plenty of other options, like OpenHab or HomeAssistant (along with their caveats). If you want something that supports multiple homes, has a driver model similar to SmartThings and Hubitat, has a reasonable robust UI and apps for control, multi-user support, and a security system that still works offline, and a bunch of spare computing resources then Arcus might be the right option.
I'd also mention that computing resources continue to get very cheap - one could buy an older laptop, perhaps a ThinkPad to run Arcus for not a terribly large amount of money.

Already use Hubitat.... I'm just looking to get away from proprietor FW code and actually do what I want it do.

@sgrayban You mean the code on the hub? Arcus struggles with the same problem at the moment, since the code for the zigbee and zwave controllers (e.g. the part that puts zigbee and zwave messages onto the serial bus) is not open source. Thankfully there's some good open source efforts (mainly openhab and zsmartsystems) which i think can be leveraged to get to an 80% solution.
I'm also thinking about adding MQTT support to Arcus so that it can be integrated with home assistant. Anyway, this is going pretty far off the topic of this original issue, so either start a thread on livingwithiris or send me an email if you want to discuss further.

Hey Andrew, is it normal to have a 404 not found when I access the UI?

It appears that you didn't set ARCUS_DOMAIN_NAME or fill it out in the setup script, so the ui-service setup a virtualhost of hub.arcussmarthome.com which isn't in public DNS.
Arcus requires a public-facing domain name, as it is HTTPs only and uses LetsEncrypt to automatically issue certificates - if the domain name is not resolvable, or the IP address and port it points to not reachable, then it will not be able to setup a certificate.
Since you've had issues getting setup-local to run, try
<EMAIL_ADDRESS>ARCUS_DOMAIN_NAME='arcus.example.com' ARCUS_SUBNET="<IP_ADDRESS>-<IP_ADDRESS>" bash ./script/shared-config.sh (with appropriate values entered in)
and then microk8s.kubectl apply -f overlays/local-production-local/

I see what your saying, but before I go much further, you telling me I need a valid domain name to attach to my server for the arcus service to resolve? If so, any suggestions. I used to pay for a domain name but not anymore.

Got a new one for you:
 sudo ./setup-hubkeystore.sh
Creating hub-keystore...
unable to load key
139932716863936:error:0909006C:PEM routines:get_name:no start line:../crypto/pem/pem_lib.c:745:Expecting: ANY PRIVATE KEY

I've checked, the key files are empty and I've tried adding debug lines in the script to list the contents of the files as the script is running but is empty as well. Kinda frustrating. Can't even get to what I'm trying to do because I can't get past the setup process due to the errors I've encountered.

You're seeing that error because the certificate didn't get issued - are you able to login to the Arcus UI without having to click through a certificate warning?
There's two other scripts I probably forgot to include in the setup instructions:
./useprodcert.sh (tells the system to use letsencrypt prod instead of staging, once you are confident in your network/DNS)
./setup-hubtruststore.sh (sets up the hub server tls key/cert based on the prod cert - it's in a different format and thus has to be converted periodically).
also, I understand your frustration in getting this up. I spend 20+ hours getting Arcus to work when I first started out, and it was not as functional or reliable as what these scripts offer. Unfortunately, the original marathon configuration was not open sourced, so there was a lot that had to be re-considered/learned in order to adapt this to something that someone else could get working. I would very much appreciate your help on documenting or closing any gaps you find, as right now there a lot of people struggling but I haven't been able to commit the same level of effort into this aspect of the project recently.

Well I can't persay login to the UI. However I do get to the website without the certificate warning. I haven't ran useprodcert.sh. I followed the instructions and edited the file to change staging to prod. I'll try today before I go to work. It's going to take me a little bit. I'm not that familiar with Yaml so I'm having to learn it. Nor am I a 100% on Linux. I didn't start playing with it until a few years ago. Got a better understanding of moving my way around the CLI. Then on top of it there are many new packages and different approaches to running services. I'm more than willing to help out getting this running. Just gotta play catchup. Probably wouldn't hurt if I can get some time to pour through the source code myself. And see what's doing what. All the errors are the frustrating thing. However once I can understand where they are coming from and what causes them. It makes things a little easier to identify them.
Hang in there. Once I can get this going, I'll help where I can.

Well I can't persay login to the UI. However I do get to the website without the certificate warning.

So you get to a login page? You need to create an account. Unfortunately the version that is currently up has a bug and you'll have to fiddle around with reloading the page to get past that step. There's a change that should be landing in the next few days to fix this.

I haven't ran useprodcert.sh
I don't understand how you wouldn't be getting a certificate warning then. Until you run useprodcert.sh you will be using the staging cert, which your browser won't trust.

It's going to take me a little bit ... It makes things a little easier to identify them.
That's totally fine.

Both were causing errors. But I figured out the problem.

Ah yes! I thought I had documented that - when you use microk8s there's no kubectl command, bur rather there's microk8s.kubectl. So you need to be able to vary the command to call depending on where you're using k8s.

I need to pick your brain from here though. So now by all means it should be up and running. However I have no way of logging into the web ui at the moment nor can I SSH into my hub. Did you have any issues here?

I recommend looking at https://github.com/arcus-smart-home/arcusplatform/tree/master/tools/hubdebug and https://github.com/arcus-smart-home/arcusplatform/blob/master/docs/hub.md. I have a pre-packaged jar which you can use to replace the hub trust store, but regrettably it's not publicly accessible. Let me see about uploading that.
If you run into any specific issues, I'll try to follow up on these. For the UI I'd recommend looking at your brower's developer tools since that will show any websocket issues.

This is what I mean about not being able to SSH into my Hub using the password with my debug key on a USB stick plugged into the Hub.
kouruu@arcus:~/arcus-k8/secret$ ssh<EMAIL_ADDRESS><EMAIL_ADDRESS>password:
Permission denied, please try again.
<EMAIL_ADDRESS>password:
Permission denied, please try again.
<EMAIL_ADDRESS>password:
<EMAIL_ADDRESS>Permission denied (publickey,password).
kouruu@arcus:~/arcus-k8/secret$ kz58!~Eb.RZ?+bqb

Of course trying with this password as stated in the MD file.
The second doc won't do me any good unless I can get past the first step. I've confirmed it's a V2 Hub but sadly the key they gave doesn't work with my hub.

I've confirmed it's a V2 Hub but sadly the key they gave doesn't work with my hub.
I have a dozen V2 hubs and haven't seen that issue before, except when I was trying to login to the hub. Can you provide your hub id (e.g. XXX-12345)? The password for the v3 hub was intially wrong, but we were able to get this sorted out thanks to the former Iris team! Please remember that the v2 hub is a centralite IH200 (e.g. a white square box) and the third generation is an Great Star IH300 (a circular white device). There are other models, but I doubt you have one.

Another thing I noticed, Create Account doesn't work on the webui login either.
Can you clarify what exactly you're seeing? There is a known issue where it asks you to setup pro monitoring and you have to reload a few times - it's a bit tricky to explain the work around, but we're waiting for the fix to that to land. Can you provide screenshots (or preferably, specific technical details beyond what you've described)?

the hub is a IH200
LWG-1759
The website may have to wait. I tried to rerun the installation now that I have a domain name setup with my system and trying to get my production certificate to revalidate. Kinda broke it at the moment and Google Chrome thinks its an attacker.

the hub is a IH200

Hm, I'm not sure what to think of your hub - the SSH server doesn't start until the key is recognized, and the password isn't configurable. Are you sure that you're logging into the right box? What happens if you disconnect it and try to SSH in? I think some more basic troubleshooting is in order.

Subject: Kubernetes Ingress Controller Fake Certificate

Yes, your browser has cause for alarm - don't accept this certificate. You're seeing this because cert-manager was not able to get a valid staging/production certificate. You'll need to make sure your system is reachable externally, and that cert-manager is working (look at kubectl log to understand what's going on).
I'm sorry you're having trouble getting this up - it's been quite an experience for me to get Arcus working, and I hope to get these issues worked out and documented or fixed shortly. While the software and concepts in Arcus are fairly mature, the infrastructure to host Arcus is relatively immature since it's being recreated in the open source version on different technology (Kubernetes instead of Apache Marathon).

Well I had it once but when I reran the script, it basically invalidated the first script. I got that part working again. I'm fixing to put a config file on my hub stick to see if I can link it to my setup to get it anywhere further. As to the answer to your question. my memory stick with the debug key allows it to attempt to SSH without it the connection refuses.

Regarding the hub, can you try a factory reset (hold the reset button for 30 seconds)? It sounds like something is wrong with your hub - since the key is being accepted, but you are unable to login.

Haven't had a chance to mess with it past few days. Busy with work. I have already reset it with the method you suggested. Didn't work. I'm just wondering if it's possible that maybe an update had to be released prior to the Iris shutdown that enabled the passwords for the hubs. (Speculating here.)
Although I know for certain that password definitely does not work with this hub.

No, I don't think it's a version issue. Let me reach out to some folks and see if they can help. I have a dozen hubs, some of which are running really old firmware, and that password still works. I believe you can put the hub firmware on a USB stick and have it update from that file automatically, but in practice I've never seen that work.
You could connect to the hub over serial console and see if there's any messages there (you'd have to get a USB UART and connect it to J1 (see http://forum.livingwithiris.com/topic/4161-hacking-the-20-hub/).
If this doesn't work, it may be easier to just get another hub.

Ok....
So I bought another Hub. Still giving me a permission denied when I try to SSH into it using the password. Same as before, I've put the debug key on the USB that matches the hub. But it does the same exact thing as the other hub. Unless there is an unwritten step that I'm missing here, I now have 2 hubs that are utterly useless.

All the steps are documented on https://github.com/wl-net/arcusplatform/blob/master/tools/hubdebug/hub_debug_keys _and_ssh_README.txt
I'd like to put something step by step (with pictures/screenshots), but thus far it hasn't really been an issue.

Andrew,
Up to this point I really appreciate all the help you have provided me to get this far. I could not have done this without you.
That said, I have done everything that page has said to do to SSH into my hubs. As can be seen in the screen shots, I have the dbg key for the hub I was working on and the other one my Putty terminal where I was logging in as root and using the password on that page for V2 hubs. What I know is I have tried this on 2 V2 Hubs, one I just bought. I also tried adding a configuration to it. I've tried on 2 different USB drives made sure both were formatted to FAT32. 1 drive is a 32Gb SanDisk. The other is a Transcend 2Gb which is fairly older. Wasn't sure if the Hub may not have supported the newer Dongle. Tried to rule everything out. I know having the dbg key for either Hub allows me the option to SSH in. Without which it gives me a Connection Refused. I just get stuck on the password part because every time I've tried the given password, and even possible combinations incase there was a typo, it gives me Access Denied. :-/

I'm still at a loss for what's happening here - I'd like to minimize a few other variables just to be sure:

Where and how are you copying the password? Some applications treat the "!" as a special character, so that could be a factor. I recommend going to the txt file, explicitly selecting the password and copying it.
Terminal software - I have not tested putty, but believe it should work. If you want to replicate what I've been working off of, I recommend trying Fedora 30 with gnome-terminal.
Hub and factory reset: since your hub does appear to be starting the SSH sever, I don't think this is a factor, but please hold down the reset button for 30 seconds to completely reset the hub. Once this is complete, you should get an SSH Host Key mismatch when connecting and you'll need to remedy that. If you do not see this warning, then it could mean that something else is wrong.

I also tested a few additional things locally, and I don't believe you need to include the cfg file or anything beyond what you've described. If you're curious, here's the SSH log when connecting:
https://gist.github.com/AndrewX192/a61b636d06372acb15a85611bf10c8e4

Where and how are you copying the password? Some applications treat the "!" as a special character, so that could be a factor. I recommend going to the txt file, explicitly selecting the password and copying it.

I've tried copy paste and typing it in. Even tried copying to text file and copied and typed from there into the password field. I've also typed the password onto the command line in putty to see what characters were popping out, just incase it was a different character set.

Terminal software - I have not tested putty, but believe it should work. If you want to replicate what I've been working off of, I recommend trying Fedora 30 with gnome-terminal.

I've tried in Putty to directly connect to it and I've also had a putty session opened to my Arcus VM and tried to use ssh from there. See below.

Hub and factory reset: since your hub does appear to be starting the SSH sever, I don't think this is a factor, but please hold down the reset button for 30 seconds to completely reset the hub. Once this is complete, you should get an SSH Host Key mismatch when connecting and you'll need to remedy that. If you do not see this warning, then it could mean that something else is wrong.

Tried this multiple times with both devices. In Putty, I just have to accept the new key. While using ssh on my Linux VM, I have to clear it out of the hosts file. Thanks for confirming that I'm not typing the password wrong, But I do admit, a bit frustrating for this to happen to me on 2 hubs. I did a debug ssh on my Linux VM like you had done if it could give any different clues as to whats going on. I'm suspecting the fact that I can't log into this hub is the main reason I can't get anywhere past the Login/Signup on the Web interface that I have forward facing.
kouruu@arcus:~$ ssh<EMAIL_ADDRESS>-vv
OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "<IP_ADDRESS>" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to <IP_ADDRESS> [<IP_ADDRESS>] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/kouruu/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/kouruu/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/kouruu/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/kouruu/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/kouruu/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/kouruu/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/kouruu/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/kouruu/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3
debug1: Remote protocol version 2.0, remote software version dropbear_2014.63
debug1: no match: dropbear_2014.63
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to <IP_ADDRESS>:22 as 'root'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm<EMAIL_ADDRESS>debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm<EMAIL_ADDRESS>debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256<EMAIL_ADDRESS>debug2: host key algorithms: ssh-rsa
debug2: ciphers ctos: aes128-ctr,3des-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes256-cbc,twofish256-cbc,twofish-cbc,twofish128-cbc
debug2: ciphers stoc: aes128-ctr,3des-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes256-cbc,twofish256-cbc,twofish-cbc,twofish128-cbc
debug2: MACs ctos: hmac-sha1-96,hmac-sha1,hmac-md5
debug2: MACs stoc: hmac-sha1-96,hmac-sha1,hmac-md5
debug2: compression ctos: zlib,zlib@openssh.com,none
debug2: compression stoc: zlib,zlib@openssh.com,none
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm<EMAIL_ADDRESS>debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha1 compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha1 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:9fayb8JDgOn9dNUE1TC7IsEWZmQjhXIAY+DXzBKDw+s
The authenticity of host '<IP_ADDRESS> (<IP_ADDRESS>)' can't be established.
RSA key fingerprint is SHA256:9fayb8JDgOn9dNUE1TC7IsEWZmQjhXIAY+DXzBKDw+s.
Are you sure you want to continue connecting (yes/no)? yes
Failed to add the host to the list of known hosts (/home/kouruu/.ssh/known_hosts).
debug2: set_newkeys: mode 1
debug1: rekey after<PHONE_NUMBER> blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey after<PHONE_NUMBER> blocks
debug2: key: /home/kouruu/.ssh/id_rsa ((nil))
debug2: key: /home/kouruu/.ssh/id_dsa ((nil))
debug2: key: /home/kouruu/.ssh/id_ecdsa ((nil))
debug2: key: /home/kouruu/.ssh/id_ed25519 ((nil))
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/kouruu/.ssh/id_rsa
debug1: Trying private key: /home/kouruu/.ssh/id_dsa
debug1: Trying private key: /home/kouruu/.ssh/id_ecdsa
debug1: Trying private key: /home/kouruu/.ssh/id_ed25519
debug2: we did not send a packet, disable method
debug1: Next authentication method: password
<EMAIL_ADDRESS>password:
debug2: we sent a password packet, wait for reply
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
<EMAIL_ADDRESS>password:
debug2: we sent a password packet, wait for reply
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
<EMAIL_ADDRESS>password:
debug2: we sent a password packet, wait for reply
debug1: Authentications that can continue: publickey,password
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
<EMAIL_ADDRESS>Permission denied (publickey,password).
kouruu@arcus:~$ kz58!~Eb.RZ?+bqb

I'm suspecting the fact that I can't log into this hub is the main reason I can't get anywhere past the Login/Signup on the Web interface that I have forward facing.

You should be able to create an account and get to the step where you add a hub (entering a hub id) without needing to have a hub setup. The two do not need to talk to each other until that point. If you still have trouble getting the platform/ui/login/registration to work, let me know.
Re the hub, I noticed that your hub reports that it is using "dropbear_2014.63", whereas mine typically report a 2016 version string, suggesting that you're using an older version of firmware. I only have a few hubs out of their boxes and ready to test against now, and many of them are hacked apart (e.g. extra wires attached) or otherwise not in a great place to test against, but I did verify that I have been able to get the firmware off of a hub using the 2014 version of dropbear. I also confirmed that the root password hash for this version of the firmware is the same as the current version.
There's one last thing we can try, and that is updating the firmware. Send me an email asking for it, and I'll get you a firmware image - then follow the instructions on https://github.com/wl-net/arcusplatform/blob/master/tools/hubdebug/hub_debug_keys _and_ssh_README.txt to attempt to update.
If this doesn't work, then I see a few different solutions:

I can expose a hub SSH server to you temporarily for the purpose of verifying that your password works.
I can mail you a known working hub in exchange for any non-working hubs (which I'll find a solution for)
You can get a USB / Serial interface cable and solder on a header to J1 and attempt to troubleshoot further yourself
You could also instruct the hub to connect back to you over HTTP using the cfg file and potentially update/compromise the system that way.

FYI, while I don't believe this is a critical error, I do see "Failed to add the host to the list of known hosts (/home/kouruu/.ssh/known_hosts)." in your error log.

This is what happens every time I try to create an account on the web service. I have tried every kind of browser (Chrome, Firefox, Edge, Safari, and IE). Obviously, I don't have an account setup. I wouldn't be mentioning it as an impasse if it was. I sent you an email in regards to the firmware. Only reason that one was so old because when I bought it, it was supposed to be new in the box. The other Hub I have may have a newer version on it as I got this while Iris was still active. Just haven't bothered checking it as they are both producing the same results.

I've got four more hubs in box (mostly that shipped in ProMonitoring Starter Kits) that I'm going to try. I found out today that some really old hubs used a different password, but it's going to some time to locate that password. Short term, I would recommend trying to update the hub firmware with the image I sent you.
I just tested signup on my dev cluster (which is running HEAD version of arcus-k8 and containers) and was able to signup without an issue. Can you open your browser developer tools and try creating an account again and note any request/response from the /account/CreateAccount endpoint?
I suspect that the backend handling the request to create an account is unavailable / unable to talk to the database, and that the front-end is treating that as a generic "you already registered that email" condition. Please note that email addresses must be unique, but phone numbers do not have to be (which is actually very useful for testing)!
The logs for the client-bridge and platform-services deployments should tell you what is happening.

WOW you guys are already testing hubs ? Damn..... that's really cool. I can wait for a production write up !!

I've been using Arcus since April 7th, shortly after the shut down, to some extent (it took about a month to get it to run reliably with push notifications and everything). I've been meaning to put together some writeups but I've not been able to make that a priority recently.

So you are reusing the old Iris hubs for this I gather ?

Yes, the old hubs connect to the new platform with minimal modifications (it is necessary to replace the trust store with one that contains the certificate authority of LetsEncrypt, instead of the old IRIS root CA). I have a prototype of the IRIS firmware running on a Raspberry PI with dongles (although one of the radios doesn't work), and have also been working to rebuild the firmware and re-implement the zigbee/zwave stack on the hubs in order to make those fully open source as well.

That's very encouraging !! I really hope you do a write up on all the steps because I know a few friends of mine that would love to get involved with this.

@Kouruu I just tested four more hubs, all of which have the new IRIS logo, and did not have any issue logging into them.
@sgrayban there is some preliminary documentation on https://github.com/wl-net/arcusplatform/tree/master/docs, but I haven't had time to fully flush it out. I've mostly been trying to get arcus-k8 to work as a simple means to get arcusplatform up and running, in the hopes that people could contribute once they got that working.

@AndrewX192 what is missing still ?

Andrew, I think we need to post that Bin file with the Debug keys. After the update, I was able to login to the Hub.
As you can see in the debug, I indeed have an access issue I need to figure out and fix. However, I'm logged into the hub.

@Kouruu awesome, glad to hear that the update worked appropriately. I see based on your browser console that CORS is not being set properly - can you show me the output of the network tab? I would also check to make sure that CORS_ORIGINS is set properly in your configmap, and restart (kubectl delete pod <>) client-bridge to pick up the change.
@sgrayban I'll can back to you with a more detailed response, but tl;dr most stuff is working in arcus that didn't depend on cloud-hosted solutions. Some additional reliability and setup improvements (to avoid all the comments/open issues on this github project) would be great, as well as bringing back grafana for metrics, fixing some problems with istio treating cassandra traffic as grpc, etc.
agent wise, we cannot currently rebuild the firmware on the hub (e.g. to patch/update things), and the zigbee/zwave controller code could not be released due to silicon labs licensing. These parts need to be replaced with open source alternatives.
larger platform wise some sort of smart apps platform (probably in the groovy DSL that arcus already has), integrations with oauth, and some more complex rules/scheduling support would be great. I've started writing drivers for the Aeotec multisensor6 and other devices, and I think it should be relatively simple to port hubitat/smartthings drivers over.

I already write drivers for Hubitat....
I guess what I need to do sometime soon is try and build a new server to compile this and then get a few hubs to work with unless you have a better solution.

As requested. Might need a refresh for CORS ORIGINS location as it has been a spell since I compiled the server. My job demands many hours of me so I only have a little time in the evenings to work on this.

@sgrayban since you already write drivers, it might be worth looking at the Arcus driver model, example: https://github.com/arcus-smart-home/arcusplatform/blob/master/platform/arcus-containers/driver-services/src/main/resources/ZB_SmartThings_MultipurposeSensorV4_2_3.driver
@Kouruu you'll need to show the response from the server - there should be a CORS policy exposed that will detail what it's set to. Most likely it's set to the default of arcussmarthome.com. I recommend running ./script/shared-config.sh and answering the questions, followed by ./kustomize build overlays/local-production-local/ | microk8s.kubectl apply -f -

My job demands many hours of me so I only have a little time in the evenings to work on this.

Same. This is 100% a spare time project. Any assistance I'm providing here is best-effort. There are some exciting things happening with Arcus, but for now there's very limited support available.

Only difference I found on mine was the file was named iris2-system-1.0.12.jar

You are using an old version of the agent. The version number should match exactly. I don't think the hubos includes a newer version of the agent - you might try doing a factory reset to confirm that. Otherwise, I'll probably need to get you updated copies of the arcus agent in order to get it working. To date, all of my arcus deployments have been on hubs that were online and updated until March 31st, thus this hasn't been an issue so far.

So I've done a factory reset, without the bin on there and it reverted back to its old self. I put the bin back on and did a reset and it allowed me to log in again. but still has the old files. I noticed a log that used /usr/bin/update -f 'file:///data/iris/data/tmp/hubOS.bin' with update status so I tried that and it gave me this:
root@LWQ-7419:/var/volatile/tmp# /usr/bin/update -f 'file:///data/iris/data/tmp/hubOS.bin'
Downloading file...done
Unable to open firmware file /tmp/upload.bin
Error validating firmware file!

So I've done a factory reset, without the bin on there and it reverted back to its old self. I put the bin back on and did a reset and it allowed me to log in again. but still has the old files. I noticed a log that used /usr/bin/update -f 'file:///data/iris/data/tmp/hubOS.bin' with update status so I tried that and it gave me this:

Ah, your hub probably only updated one of the update partitions. Thus, when you did a factory reset it restored the really old firmware. I'm not sure what hubOS.bin is on your hub - you should invoke update with a path to the file on your flash drive if possible. It may be possible to specify the other recovery partition, so that you can update the backup copy of /data. The agent is designed to connect to a server and pull down an new agent update, but I haven't figured out how to stand that up yet, so there's not a good way to do it. Once I figure that out, there should be a good way to go to a website, enter your hub ID and download a few files to a flash drive which can be used to completely automate this process.

So one of the things I did when I followed the instructions was I port forwarded on my routing software the ports for the 2 ip's. This was listed on the page:

This generally looks fine, but note that "8-" should be "80". Also you may need to masqurade traffic, and that 172.16.6.* may not be a good choice of network space for you (it is appropriate for my network, but mine is not ordinary). Given that you are able to reach the UI, I doubt this is a the problem. I actually do not follow this approach anymore, and instead have a gateway at my edge that routes traffic to the appropriate backend based on TLS SNI. This is conceptually easier to reason about than iptables/netfilters and provides me more flexibility for dev/staging/prod instances.

BTW the Developer Tools just says Failed to load response data.

It looks like the server isn't responding to your request. Did you look at the log for client-bridge? I are all of your pods running?

kouruu@arcus:~/arcus-k8$ microk8s.kubectl get pods
NAME                                    READY   STATUS     RESTARTS   AGE
alarm-service-769b768b9b-md6gl          2/2     Running    24         22d
cassandra-0                             2/2     Running    12         22d
client-bridge-8658fc87fd-wsxmg          2/2     Running    23         22d
driver-services-56fc56c7b6-d249z        2/2     Running    694        22d
history-service-bb56d4844-t7hbz         2/2     Running    22         22d
hub-bridge-86789665c4-rtfff             2/2     Running    15         22d
kafka-0                                 2/2     Running    21         7d18h
notification-services-b4bcd9b59-cmhbw   0/2     Evicted    0          7d22h
notification-services-b4bcd9b59-kmmxd   0/2     Evicted    0          22d
notification-services-b4bcd9b59-pmgj2   0/2     Init:0/1   0          7d18h
platform-services-77f7d6598d-7fstw      2/2     Running    23         22d
rule-service-6849b6f55d-g4sk6           2/2     Running    22         22d
scheduler-service-68488bd499-rdcvr      2/2     Running    24         22d
subsystem-service-65c5576966-tnpqp      2/2     Running    23         22d
ui-server-55f99d45fc-7lhmt              2/2     Running    12         22d
zookeeper-5ff79bfcd5-gnpwj              2/2     Running    12         22d

Oh I didn't use the iptables above, I wanted to rule that out. That was from the documentation. I setup an internal gigabit home network to get away from crapTT's limited network capacity and I host pfSense on a Dell R710 along with a DNS adblocker. I have those ports forwarded on there appropriately. As well as I have another Server that I built that I host many other VMs including Home Assistant and Arcus.
The best I could tell is the server is giving me an authentication denied or some sort.
I'll edit post after I look up how to get log for client-bridge

I'll edit post after I look up how to get log for client-bridge

microk8s.kubectl logs client-bridge-8658fc87fd-wsxmg

D0820 01:10:24.075 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:10:54.075 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
E0820 01:11:06.716 tion-1     c.d.d.core.ControlConnection] [Control connection] Cannot connect to any host, scheduling retry in 1000 milliseconds
W0820 01:11:07.453 ecutor     c.i.p.cluster.ClusterService] Error updating heartbeat table
com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (no host was tried)
        at com.datastax.driver.core.exceptions.NoHostAvailableException.copy(NoHostAvailableException.java:84)
        at com.datastax.driver.core.exceptions.NoHostAvailableException.copy(NoHostAvailableException.java:37)
        at com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37)
        at com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:245)
        at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:68)
        at com.iris.platform.cluster.cassandra.CassandraClusterServiceDao.heartbeat(CassandraClusterServiceDao.java:211)
        at com.iris.platform.cluster.ClusterService.heartbeat(ClusterService.java:124)
        at com.iris.platform.cluster.ClusterService.lambda$onStarted$0(ClusterService.java:82)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (no host was tried)
        at com.datastax.driver.core.RequestHandler.reportNoMoreHosts(RequestHandler.java:210)
        at com.datastax.driver.core.RequestHandler.access$1000(RequestHandler.java:46)
        at com.datastax.driver.core.RequestHandler$SpeculativeExecution.findNextHostAndQuery(RequestHandler.java:274)
        at com.datastax.driver.core.RequestHandler.startNewExecution(RequestHandler.java:114)
        at com.datastax.driver.core.RequestHandler.sendRequest(RequestHandler.java:94)
        at com.datastax.driver.core.SessionManager.executeAsync(SessionManager.java:132)
        ... 11 common frames omitted
E0820 01:11:07.717 tion-1     c.d.d.core.ControlConnection] [Control connection] Cannot connect to any host, scheduling retry in 2000 milliseconds
D0820 01:11:24.080 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:11:54.081 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:12:24.081 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:12:54.081 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:13:24.081 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:13:54.082 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:14:24.082 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:14:54.082 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:15:24.082 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:15:54.082 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
E0820 01:16:06.853 tion-0     c.d.d.core.ControlConnection] [Control connection] Cannot connect to any host, scheduling retry in 1000 milliseconds
W0820 01:16:07.453 ecutor     c.i.p.cluster.ClusterService] Error updating heartbeat table
com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (no host was tried)
        at com.datastax.driver.core.exceptions.NoHostAvailableException.copy(NoHostAvailableException.java:84)
        at com.datastax.driver.core.exceptions.NoHostAvailableException.copy(NoHostAvailableException.java:37)
        at com.datastax.driver.core.DriverThrowables.propagateCause(DriverThrowables.java:37)
        at com.datastax.driver.core.DefaultResultSetFuture.getUninterruptibly(DefaultResultSetFuture.java:245)
        at com.datastax.driver.core.AbstractSession.execute(AbstractSession.java:68)
        at com.iris.platform.cluster.cassandra.CassandraClusterServiceDao.heartbeat(CassandraClusterServiceDao.java:211)
        at com.iris.platform.cluster.ClusterService.heartbeat(ClusterService.java:124)
        at com.iris.platform.cluster.ClusterService.lambda$onStarted$0(ClusterService.java:82)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (no host was tried)
        at com.datastax.driver.core.RequestHandler.reportNoMoreHosts(RequestHandler.java:210)
        at com.datastax.driver.core.RequestHandler.access$1000(RequestHandler.java:46)
        at com.datastax.driver.core.RequestHandler$SpeculativeExecution.findNextHostAndQuery(RequestHandler.java:274)
        at com.datastax.driver.core.RequestHandler.startNewExecution(RequestHandler.java:114)
        at com.datastax.driver.core.RequestHandler.sendRequest(RequestHandler.java:94)
        at com.datastax.driver.core.SessionManager.executeAsync(SessionManager.java:132)
        ... 11 common frames omitted
E0820 01:16:07.854 tion-0     c.d.d.core.ControlConnection] [Control connection] Cannot connect to any host, scheduling retry in 2000 milliseconds
D0820 01:16:24.083 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:16:54.083 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:17:24.083 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:17:54.083 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:18:24.084 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:18:54.084 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:19:24.084 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:19:54.085 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:20:24.085 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:20:54.085 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:21:24.086 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:21:54.086 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:22:24.086 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:22:54.086 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:23:24.086 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:23:54.087 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:24:24.087 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:24:54.087 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:25:24.087 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:25:54.088 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:26:24.088 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:26:54.088 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:27:24.088 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:27:54.089 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:28:24.089 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:28:54.089 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:29:24.089 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:29:54.090 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:30:24.090 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:30:54.090 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:31:24.090 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:31:54.090 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:32:24.091 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:32:54.091 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:33:24.091 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:33:54.091 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:34:24.092 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:34:54.092 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:35:24.092 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:35:54.092 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:36:24.093 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:36:54.093 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:37:24.093 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:37:54.094 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:38:24.094 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:38:54.094 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:39:24.095 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:39:54.095 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:40:24.096 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:40:54.096 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:41:24.096 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:41:54.097 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:42:24.097 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:42:54.097 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:43:24.098 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:43:54.098 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:44:24.098 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:44:54.099 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:45:24.099 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:45:54.099 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:46:24.100 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:46:54.100 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:47:24.100 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:47:54.101 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:48:24.101 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:48:54.101 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:49:24.102 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:49:54.102 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:50:24.102 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:50:54.103 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:51:24.103 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:51:54.103 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:52:24.104 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:52:54.104 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:53:24.104 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:53:54.105 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:54:24.105 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:54:54.105 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:55:24.105 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:55:54.106 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:56:24.106 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:56:54.106 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:57:24.106 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:57:54.107 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:58:24.107 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:58:54.107 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:59:24.107 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 01:59:54.108 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:00:24.108 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:00:54.108 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:01:24.108 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:01:54.109 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:02:24.109 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:02:54.109 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:03:24.109 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:03:54.109 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:04:24.110 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:04:54.110 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:05:24.110 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:05:54.110 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:06:24.111 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:06:54.111 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:07:24.111 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:07:54.112 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:08:24.112 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:08:54.112 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:09:24.112 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:09:54.112 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:10:24.113 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:10:54.113 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
E0820 02:11:10.456 tion-0     c.d.d.core.ControlConnection] [Control connection] Cannot connect to any host, scheduling retry in 1000 milliseconds
E0820 02:11:11.457 tion-0     c.d.d.core.ControlConnection] [Control connection] Cannot connect to any host, scheduling retry in 2000 milliseconds
D0820 02:11:24.113 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:11:54.113 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:12:24.114 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:12:54.114 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:13:24.114 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:13:54.114 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:14:24.115 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:14:54.115 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:15:24.115 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:15:54.115 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
E0820 02:16:10.850 tion-1     c.d.d.core.ControlConnection] [Control connection] Cannot connect to any host, scheduling retry in 1000 milliseconds
E0820 02:16:11.854 tion-1     c.d.d.core.ControlConnection] [Control connection] Cannot connect to any host, scheduling retry in 2000 milliseconds
D0820 02:16:24.116 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:16:54.116 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:17:24.116 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:17:54.116 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:18:24.117 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:18:54.117 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:19:24.117 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:19:54.117 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:20:24.117 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:20:54.118 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:21:24.118 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:21:54.118 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:22:24.118 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:22:54.119 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:23:24.119 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:23:54.119 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:24:24.119 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:24:54.120 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:25:24.120 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:25:54.120 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:26:24.120 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:26:54.120 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:27:24.121 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:27:54.121 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:28:24.121 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:28:54.121 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:29:24.122 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:29:54.122 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:30:24.122 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:30:54.122 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:31:24.123 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:31:54.123 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:32:24.123 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:32:54.123 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:33:24.124 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:33:54.124 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:34:24.124 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:34:54.124 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:35:24.124 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:35:54.125 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:36:24.125 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:36:54.125 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:37:24.125 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:37:54.126 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:38:24.126 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:38:54.126 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:39:24.126 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:39:54.127 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:40:24.127 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:40:54.127 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:41:24.127 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:41:54.127 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:42:24.128 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:42:54.128 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:43:24.128 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:43:54.128 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:44:24.129 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:44:54.129 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:45:24.129 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:45:54.129 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:46:24.130 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:46:54.130 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:47:24.130 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:47:54.130 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:48:24.131 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:48:54.131 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:49:24.131 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:49:54.131 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:50:24.131 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:50:54.132 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:51:24.132 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:51:54.132 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:52:24.132 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:52:54.133 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:53:24.133 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:53:54.133 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:54:24.133 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:54:54.133 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:55:24.134 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:55:54.134 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:56:24.134 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:56:54.134 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:57:24.135 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:57:54.135 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:58:24.135 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:58:54.135 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:59:24.135 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 02:59:54.136 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:00:24.136 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:00:54.136 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:01:24.136 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:01:54.137 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:02:24.137 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:02:54.137 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:03:24.137 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:03:54.138 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:04:24.138 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:04:54.138 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:05:24.138 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:05:54.139 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:06:24.139 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:06:54.139 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:07:24.139 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:07:54.139 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:08:24.140 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:08:54.140 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:09:24.142 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:09:54.143 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:10:24.143 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:10:54.143 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
E0820 03:11:15.026 tion-0     c.d.d.core.ControlConnection] [Control connection] Cannot connect to any host, scheduling retry in 1000 milliseconds
E0820 03:11:16.026 tion-0     c.d.d.core.ControlConnection] [Control connection] Cannot connect to any host, scheduling retry in 2000 milliseconds
D0820 03:11:24.143 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:11:54.144 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:12:24.144 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:12:54.144 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:13:24.144 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:13:54.145 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:14:24.145 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:14:54.145 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:15:24.145 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:15:54.146 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
E0820 03:16:15.424 tion-1     c.d.d.core.ControlConnection] [Control connection] Cannot connect to any host, scheduling retry in 1000 milliseconds
E0820 03:16:16.425 tion-1     c.d.d.core.ControlConnection] [Control connection] Cannot connect to any host, scheduling retry in 2000 milliseconds
D0820 03:16:24.146 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:16:54.146 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:17:24.146 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:17:54.147 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:18:24.147 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:18:54.147 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:19:24.147 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:19:54.148 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:20:24.148 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:20:54.148 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:21:24.148 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:21:54.149 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:22:24.149 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:22:54.149 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:23:24.149 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:23:54.150 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:24:24.150 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:24:54.150 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:25:24.150 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:25:54.151 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:26:24.151 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:26:54.151 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:27:24.151 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:27:54.152 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:28:24.152 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:28:54.152 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:29:24.152 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:29:54.158 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:30:24.158 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:30:54.158 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:31:24.159 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:31:54.159 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:32:24.159 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:32:54.159 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:33:24.160 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:33:54.160 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:34:24.160 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:34:54.160 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:35:24.161 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:35:54.161 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:36:24.161 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:36:54.161 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:37:24.162 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:37:54.162 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:38:24.162 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:38:54.162 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:39:24.163 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:39:54.163 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:40:24.163 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:40:54.163 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:41:24.164 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:41:54.164 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:42:24.164 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:42:54.164 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called
D0820 03:43:24.165 tchdog .i.p.h.r.HubRegistrationRegistry] HubRegistrationRegistry.timeout is called

What errors do you see in the log after trying to create an account? I bet that your client-bridge is not able to talk to cassandra, and thus it doesn't return an appropriate response. I recommend pulling down the latest code in arcus-k8 and re-running ./setup-local.sh and ./useprodcert.sh, potentially followed by rebooting the virtual machine or whatever you're running microk8s on to force all of the pods to restart. This will ensure that you're running on the latest version of all the code and dependencies.

Sorry that was hub-bridge
Arcus Client-hub log.txt
It's a big read.

Yep, you clearly have a database connectivity issue - nothing is getting through, thus you can't create an account. I recommend ensuring that you're fully up to date (e.g. git pull, ./setup-local.sh, ./useprodcert.sh, and rebooting + waiting 5-10 minutes). If the issue persists then please share a log for client-bridge and cassandra and we can troubleshoot from there.
Kubernetes and istio add a non-trivial amount of complexity, and troubleshooting can be difficult. I strongly recommend upgrading to the latest version, since many improvements have been made to these connectivity issues in the last few weeks.

Awesome, I'll be giving it a shot. If anything, this thread has worked through alot of issues and hopefully will be of great help for others trying this.

Here's a little sneak peak to keep you motivated :)

Well ain't that a teaser. I also don't know if this helps any, but I remember hearing the agent missing bits for the closed source items, but I see firmware bin files on my hub. Probably nothing, but eh.
root@LWQ-7419:/data/firmware# ls
ble-firmware-hwflow.bin     ble-firmware.bin            zigbee-firmware-hwflow.bin  zigbee-firmware.bin         zwave-firmware.bin

Yes, the firmware files are helpful - and you can continue to use Arcus without updating the hub, but in order to make Arcus a mature platform, we need to develop open source replacements to these libraries, so they can be maintained. At present the agent code can't be "linked" against the proprietary libraries since we don't know what the API looks like, but based on the commented out code I don't think that will take long to address - it will take far longer to develop drop in replacements.

Also regarding updating the agent code, take a look at this line of code in /data/agent/bin/iris-agent:
  /usr/bin/update -f 'file:///data/iris/data/tmp/hubOS.bin' && /bin/rm -rf '/data/agent' && exec /usr/bin/hub_restart 0. Perhaps if /data/agent is deleted, then it will automatically restore it from the latest version?
Alternatively, I could get you hubAgent.bin as used in:
       mv '/data/agent' '/data/agent-backup' && mkdir '/data/agent' && cd /data/agent && tar xzf '/data/iris/data/tmp/hubAgent.bin' && cd - && rm -rf '/data/agent-backup' && exec ${IRISAGENT_ALLARGS}
       echo "Installation of hub agent failed, restarting old agent..."
       rm -rf '/data/agent' && mv '/data/agent-backup' '/data/agent' ; exec ${IRISAGENT_ALLARGS}
       ;;```

/usr/bin/update -f 'file:///data/iris/data/tmp/hubOS.bin' && /bin/rm -rf '/data/agent' && exec /usr/bin/hub_restart 0

This successfully updated the code on the hub. However, I had to point hubOS.bin to the location of my usb stick.
/usr/bin/update -f 'file:///run/media/sda1/hubOS.bin' && /bin/rm -rf '/data/agent' && exec /usr/bin/hub_restart 0
Next is to work on the Website

Got to the Dashboard finally. You were right about the CORS ORIGINS. Although, I had to go about fixing it differently. I went into my local overlay file and updated everything manually. Then I applied the file and it started working. Now I just need to pair the hub. Already tried 4 times and it failed. I did the Hub keystore script and Jar'd the file on the hub. I think it's resetting during the pairing process at random times. Don't know if that's normal but I'll figure it out later.

Hey Andrew, I think I need your help one more time. I have updated the firmware on both of my hubs. And I cannot get them to pair on the website. I'm not sure if I'm doing the truststore part right. I found the truststore.jks in the irisbylowes folder. Am I assuming this is correct and to jar this with the file and load it back to the hub. Cause I have done this, on both hubs. and unfortunately, they both behave the same. Won't link with the website and periodically reset.

Did you look at the agent log in /tmp? What does it say?

Couldn't find anything about the agent log in the /tmp folder. Assuming you are talking about on my hub. It did have a agent_config log that showed what I had in my config file on the usb stick. However now I'm trying to fix other issues with my web server. Now it's not loading properly and I had an issue where I rebooted the server and the pods flooded with evicted pods. No biggie, I used this command to clear them out: sudo microk8s.kubectl get pods | grep Evicted | awk '{print $1}' | xargs microk8s.kubectl delete pod Still no connecting to my hub though.

There should be a file similar to "hubAgent.log" on the hub, which will explain what's happening. I suspect one of the file permissions in /data/agent/libs is set such that the agent can't read the file - it's a fairly common mistake.

Now it's not loading properly and I had an issue where I rebooted the server and the pods flooded with evicted pods.

Unfortunately Kubernetes is fairly immature here - I've had mixed success with rebooting hosts. It's typically better to completely rebuild the cluster each time you need to restart/update/etc. This requires a non-trivial amount of automation. That said, I have a staging and prod instance that have recently been relatively good about rebooting (it takes about 15 minutes each week to reboot for updates)

Lastly, I got an email about a version issue with certmanager from let's encrypt. Apparently they are requiring a version update on certmanager before they start blocking. Did you get this email too?

I haven't gotten this email yet, but I am due to renew certificates soon. arcus-k8 uses cert-manager 0.7 from May. It looks like it's already been retired with a new version that isn't backward compatible. It will probably have to be upgraded.

<EMAIL_ADDRESS>Thu, Aug 29, 10:37 AM (5 days ago)
to me
We've been working with Jetstack, the authors of cert-manager, on a
series of fixes to the client. Cert-manager sometimes falls into a
traffic pattern where it sends really excessive traffic to Let's
Encrypt's servers, continuously. To mitigate this, we plan to start
blocking all traffic from cert-manager versions less than 0.8.0 (the
current semver minor release), as of November 1, 2019. Please upgrade
all of your cert-manager instances before then.
We're sending this email because this is the contact address of your
cert-manager instance at:
##.##.##.## .
Version 0.8.0 is much better but we still observe excessive traffic in
some cases. We're working with Jetstack to improve these cases. As new
versions of cert-manager are released, we will add the non-current
versions to our block list after 3 months. We strongly encourage
cert-manager users to stay up-to-date with new versions.
Also, there is an opportunity to help both Jetstack and Let's Encrypt.
Once you've upgraded, please check the logs for your cert-manager
instances from time to time. Are they making excessive requests to Let's
Encrypt (more than, say, 10 per day over multiple days)? If so, please
share details at https://github.com/jetstack/cert-manager/issues/1948 .
Thanks,
Let's Encrypt Team

My IP removed of course. This is the email I got from Let's Engcrypt.
root@LWG-1759:/var/volatile/tmp# cat hubAgent.log
performing sqlite3 integrity check...
W0903 23:41:23.276   main c.iris.agent.hal.WatchdogControl] hardware watchdog implementation: OMAP Watchdog
W0903 23:41:23.475   main c.iris.agent.hal.WatchdogControl] hardware watchdog timeouts: default=60, updated=300
W0903 23:41:23.482   main c.iris.agent.hal.WatchdogControl] hardware watchdog flags: [SETTIMEOUT, MAGICCLOSE, KEEPALIVEPING]
W0903 23:41:23.496   main c.iris.agent.hal.WatchdogControl] hardware watchdog temp: 0.0
W0903 23:41:23.514   main c.iris.agent.hal.WatchdogControl] software watchdog timeout: 300
W0903 23:41:23.534   main   c.i.a.watchdog.WatchdogService] watchdog service started
W0903 23:41:23.837   main      com.iris.agent.db.DbService] sqlite database is thread safe, enabling multi-threaded mode
W0903 23:41:23.839   main      com.iris.agent.db.DbService] sqlite write ahead log mode enabled, checkpointing every 3600000ms
W0903 23:41:35.584   main  c.iris.agent.scene.SceneService] entering scene: scene service started
W0903 23:41:36.882   main c.n.g.lifecycle.ClasspathScanner] No base packages specified - no classpath scanning will be done
W0903 23:42:03.190   zbic    c.i.a.z.d.e.EmberZigbeeDriver] ezsp stack status changed: EzspStackStatusHandler [status=0x90]

This is what I get from hubAgent.log

My IP removed of course. This is the email I got from Let's Engcrypt.

The latest revision of arcus-k8 now uses version 0.9. Please delete the old resources and upgrade (re-run setup-local.sh, followed by ./useprodcert.sh):
microk8s.kubectl delete -f https://raw.githubusercontent.com/jetstack/cert-manager/release-0.7/deploy/manifests/cert-manager.yaml

This is what I get from hubAgent.log

Please set IRIS_AGENT_LOGTYPE = dev in the configuration file, and reboot the hub. Please wait at least a few minutes before capturing the log file to provide in this issue.

Closing due to inactivity - if you have further questions or want support, please use http://forum.livingwithiris.com/forum/62-arcus/. The issue tracker is now only for tracking bugs, not support.
In the future, there will be a lot more attention to documentation to make more of this self-service.

FYI, I ended up finding the problem that resulted in the original report. This was a result of a bug in kustomize being fixed, which revealed a never discovered before error in the configuration. Fix is in https://github.com/wl-net/arcus-k8/commit/56f5e5f523234aa59bca70501ad6bc38d9cbd974


Missing IOCTL_CDROM_* constants

Summary
I noticed while trying to read from a CD drive that the IOCTL_CDROM_* constant for DeviceIoControl were missing in this crate, they do not show in the feature search page (version 0.58.0).
I'm referring to those codes https://learn.microsoft.com/en-us/previous-versions/windows/drivers/storage/cd-rom-io-control-codes.

https://kennykerr.ca/rust-getting-started/how-are-crates-built.html
Will forward to the Win32 metadata repo.


Declare postgres as vendor in tuples

Let's see if this works.

please update README.md too once you've got things settled in.

I haven't made it fully magical as most changes will get stomped by #155.

See also #156 some of the motivation.


Do not include Dialog third_party in pretty target.

Codecov Report

Merging #1475 into master will decrease coverage by 0.7%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1475      +/-   ##
==========================================
- Coverage   70.68%   69.97%   -0.71%
==========================================
  Files         142      142
  Lines       19500    19499       -1
  Branches     2383     2383
==========================================
- Hits        13783    13645     -138
- Misses       4824     4958     +134
- Partials      893      896       +3

Impacted Files
Coverage Δ

src/core/api/icmp6_api.cpp
50% <0%> (-50%)
:x:

src/core/thread/key_manager.hpp
80% <0%> (-20%)
:x:

src/core/api/ip6_api.cpp
41.93% <0%> (-17.75%)
:x:

src/core/api/thread_api.cpp
29.43% <0%> (-16.89%)
:x:

src/core/mac/mac_whitelist.cpp
75.47% <0%> (-15.1%)
:x:

examples/platforms/posix/random.c
85% <0%> (-15%)
:x:

src/core/api/netdata_api.cpp
57.44% <0%> (-14.9%)
:x:

src/core/thread/lowpan.hpp
97.36% <0%> (-2.64%)
:x:

src/ncp/ncp_base.cpp
37.1% <0%> (-1.96%)
:x:

src/core/mac/mac.cpp
79.25% <0%> (-1.19%)
:x:

... and 6 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9a175be...89dbce1. Read the comment docs.


Add support for custom key param for range aggregation

Resolves #1425

Codecov Report

Merging #1426 (361f4ff) into main (931bab8) will increase coverage by 0.00%.
The diff coverage is 98.97%.

@@           Coverage Diff           @@
##             main    #1426   +/-   ##
=======================================
  Coverage   94.22%   94.22%
=======================================
  Files         236      236
  Lines       43775    43852   +77
=======================================
+ Hits        41245    41320   +75
- Misses       2530     2532    +2

Impacted Files
Coverage Δ

src/aggregation/bucket/range.rs
96.68% <98.97%> (+0.38%)
:arrow_up:

bitpacker/src/bitpacker.rs
96.03% <0.00%> (-1.00%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 931bab8...361f4ff. Read the comment docs.


Add three 'Tutorial' sites

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@IsharabAhmed Thanks for your contribution. These resources are imho too general to be particularly helpful, especially when there are much more specific resources out there.


afterUndelete works but afterDelete does not

Having some trouble understanding why I can't get the rollup to run the appropriate CMDT records using runFromTrigger() in the afterDelete or beforeDelete trigger operation types. I have no such problem with the afterUndelete trigger, but this compounds the problem by adding back a value that was never removed by the delete.
Am I missing something about how delete triggers work? I'm happy to provide additional information to help troubleshoot.
Thanks for making this framework available and the ongoing support and development!

I dropped a recalculate button on the parent object and the button works correctly.

@clint-rosetree are you sure your trigger has before delete listed as one of the defined trigger contexts? It sounds like you're using a trigger framework, but that would still require the object the trigger is defined on to have the proper contexts set up (otherwise it simply won't run for the defined context). After delete is only necessary if you're having Apex Rollup help out with standard object merges; I would double check the trigger in question to ensure before delete is defined. Let me know!

Thanks James, I'll switch back to the before delete context for the implementation and do some more testing. Definitely have the before delete context defined, but in my testing, I was running into the "System.FinalException: Record is read-only" error with the rollup there. This is a fairly old org, so there are plenty of places for failure, so I'll investigate where that error is really originating.
Will do some more debugging and report back what I find.

Hmm I replied via email but I guess it never sent ... let me know if you end up with a stacktrace for where you were seeing that System.FinalException - I'm assuming you are using a formula field somewhere in your rollup? There must be something on the delete code path that is trying to do the wrong there. We will get this fixed!

There are some formula fields involved with this one, so that may have been a source for the read-only error. I'm in the middle of testing some of the more complex scenarios, but so far, I've been able to get the delete rollup to fire correctly by moving the Rollup.runFromTrigger() call to the before delete trigger context in a few places.🤞

I'm no longer encountering this issue in my testing. The ultimate solution was to move everything into the before delete trigger context. I thought I had tried that already, but there may have been other issues I missed at that time.
Thanks for the support, @jamessimone

No problem - happy to help!


Add PWA support, Service Worker and Manifest, plus icons.

Already talked with Evgeni via email about making QiFi a Progressive Web App. I added a Service Worker, Manifest file and icons needed by the Manifest.

Thanks a ton! I'll have a closer look next week when I have some spare time, but this looks pretty polished already!

@evgeni, have you had time to review the pull request?

This pull request is using an older version of QiFi, should I do this again with the latest version available on GitHub?

Looking at the code, you only reference file names, those didn't change. So after merging it will automatically use the latest code.

Btw, you can see a deployed merge here: https://deploy-preview-18--qifi.netlify.com/

Is it okay now, @evgeni?
I'm kind of a newbie using Git, that's why I did two commits without noticing.

I've checked it and it's totally wrong, probably because I don't know how to use Git. I'll try to fix this. So sorry :(

I think this is now fixed. Sorry, I'm a total newbie using Git.
This still has conflicts in the index.html because I'm using an older commit.

@evgeni, have you checked the changes?

Yes, I did! Merging :)


Swift 5.7 segmentation fault during silgen

Describe the bug
When using Swift 5.7, the compiler will crash when trying to compile anything containing a function like the one below.
func test(arg: Never) async { }

The same happens with any other enum with no cases.
This can also be seen here: https://swiftfiddle.com/jw3n746lkfgwxmpdqh3xqltmui
Environment

Xcode 14.0 beta 5
swift-driver version: 1.62.3 Apple Swift version 5.7 (swiftlang-<IP_ADDRESS>.8 clang-14<IP_ADDRESS>)
Target: arm64-apple-macosx13.0

It doesn’t crash on main so I guess it got fixed recently.


[PE-D][Tester D] No department command details in the feature section

No department command details in the feature section but can be found in the command summary. The bracket is also mismatching.

Labels: severity.Medium type.DocumentationBug
original: richiehx/ped#14

Duplicate of #93