My read of the link I provided is that when the eventmachine gem is installed it configures itself based on what headers it can find on the system. If libssl-dev is present, it will configure encryption.
If the puppet configuration doesn't specify an order, packages may be installed in any order. By now, you know as well as I do that the first time you run puppet on a new machine, there likely is going to be an error which is discovered after some packages install. Fix that error, and more install. Repeat until everything is installed. What that inevitably means is that the order in which packages are installed on different machines can be different, even if the end result is that all of the packages eventually are installed. This is just a theory at this point, but worth exploring. The fix may be as simple as uninstalling eventmachine manually and letting puppet install it again. I'm stopping short of doing this myself as an explicit goal of mine is to get to the point where others can resolve problems like these. - Sam Ruby On Thu, Sep 24, 2020 at 10:30 AM sebb <seb...@gmail.com> wrote: > > The login message said to reboot, so I have done this. > > However it does not appear to have helped. > > On Thu, 24 Sep 2020 at 14:28, sebb <seb...@gmail.com> wrote: > > > > On Thu, 24 Sep 2020 at 14:14, Sam Ruby <ru...@intertwingly.net> wrote: > > > > > > If you go into the board agenda tool and open the console, you will > > > see messages that it can't connect to the websocket. Things appear > > > to mostly be set up correctly: > > > > > > $ grep websocket /etc/apache2/sites-available/10-whimsy-vm-443.conf > > > ProxyPass "/board/agenda/websocket/" "wss://localhost:34234/" > > > > > > $ sudo lsof -i :34234 > > > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME > > > ruby 3430562 root 16u IPv4 160482206 0t0 TCP *:34234 (LISTEN) > > > > > > $ sudo systemctl status board-agenda-websocket.service > > > ● board-agenda-websocket.service - Whimsy Board Agenda WebSocket service > > > Loaded: loaded > > > (/etc/systemd/system/board-agenda-websocket.service; static; vendor > > > preset: enabled) > > > Active: active (running) since Thu 2020-09-24 12:56:18 UTC; 9s ago > > > Main PID: 3430562 (ruby) > > > Tasks: 8 (limit: 9541) > > > Memory: 35.5M > > > CGroup: /system.slice/board-agenda-websocket.service > > > └─3430562 /usr/local/bin/ruby > > > /srv/whimsy/www/board/agenda/daemon/wss.rb > > > > > > Sep 24 12:56:18 whimsy-vm6 systemd[1]: Started Whimsy Board Agenda > > > WebSocket service. > > > > > > Note, however, how long the websocket has been running (9s). This > > > indicates that it is dying and was restarted. Looking at the syslog > > > confirms this: > > > > > > Sep 24 13:09:07 whimsy-vm6 ruby[3435205]: terminate called after > > > throwing an instance of 'std::runtime_error' > > > Sep 24 13:09:07 whimsy-vm6 ruby[3435205]: what(): Encryption not > > > available on this event-machine > > > Sep 24 13:09:07 whimsy-vm6 systemd[1]: board-agenda-websocket.service: > > > Main process exited, code=dumped, status=6/ABRT > > > Sep 24 13:09:07 whimsy-vm6 systemd[1]: board-agenda-websocket.service: > > > Failed with result 'core-dump'. > > > Sep 24 13:09:07 whimsy-vm6 systemd[1]: board-agenda-websocket.service: > > > Scheduled restart job, restart counter is at 17895. > > > Sep 24 13:09:07 whimsy-vm6 systemd[1]: Stopped Whimsy Board Agenda > > > WebSocket service. > > > Sep 24 13:09:07 whimsy-vm6 systemd[1]: Started Whimsy Board Agenda > > > WebSocket service. > > > > > > Random googling turned up: > > > > > > https://github.com/huginn/huginn/issues/386 > > > > > > Perhaps it is a puppet sequence error, and the eventmachine gem needs > > > to be installed AFTER libssl-dev? > > > > Looks like the code is working on vm5, which has a very similar Puppet > > setup. > > The main differences are some software versions. > > > > > - Sam Ruby
