Closed majames closed 11 months ago
We were able to work around the issue by installing Watchman using the pre-built binaries (instead of using the .deb package)
$ unzip watchman-*-linux.zip
$ cd watchman-vYYYY.MM.DD.00-linux
$ sudo mkdir -p /usr/local/{bin,lib} /usr/local/var/run/watchman
$ sudo cp bin/* /usr/local/bin
$ sudo cp lib/* /usr/local/lib
$ sudo chmod 755 /usr/local/bin/watchman
$ sudo chmod 2777 /usr/local/var/run/watchman
We also had to install the libssl1.1
package as well: https://gist.github.com/joulgs/c8a85bb462f48ffc2044dd878ecaa786
Installed libssl1.1, removed watchman and reinstalled (latest version) via apt-get and it's back working.
Hello. My company uses the Metro module bundler for bundling our javascript code. After updating the docker container base image from Ubuntu 18 to 22.04 we're experiencing the startup error below causing Watchman to crash.
The odd thing is that the unix socket seems to be fine and manually restarting watchman (or the node.js process which calls into watchman) fixes the issue:
Relevant tooling versions
fb-watchman
node package --fb-watchman@2.0.1
watchman
daemon --20231008.002904.0
(installed via the .deb package distributed here)v18.16.1
Watchman log file
The watchman daemon log file seems to indicate that it fails to decode a message sent to it via the BSER protocol but I'm not sure whether that's a red herring:
Does anyone know what could be going wrong here?