I am on Mac ventura 13.0.1 (22A400)
I am trying to install watchman however it is not getting installed as a service that can be run in service/daemon mode
brew install watchman
==> Downloading https://formulae.brew.sh/api/cask.json
Warning: watchman 2023.02.13.00 is already installed and up-to-date.
To reinstall 2023.02.13.00, run:
brew reinstall watchman
However, it says that it cannot be run and loadable
brew services info watchman
watchman (homebrew.mxcl.watchman)
Running: ✘
Loaded: ✘
Schedulable: ✘
Brew services list
brew services list
Name Status User File
memcached started xxx ~/Library/LaunchAgents/homebrew.mxcl.memcached.plist
rabbitmq started xxx ~/Library/LaunchAgents/homebrew.mxcl.rabbitmq.plist
redis none
stunnel none
However I can use watchman in command line mode, but other programs that need to find watchman can't use it
Related
I tried installing the monitoring agent multiple times using both Google Cloud Console & Command Line. None of the approach worked.
My OS Version:
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
Installation Logs:
curl -sSO https://dl.google.com/cloudagents/add-monitoring-agent-repo.sh
sudo bash add-monitoring-agent-repo.sh --also-install
Error:
Err:10 https://packages.cloud.google.com/apt google-cloud-monitoring-bullseye-all Release
404 Not Found [IP: 142.250.182.206 443]
It fails because it's getting 404 from the legacy monitoring agent source list and you need the updated Cloud Ops Agent script:
curl -sSO https://dl.google.com/cloudagents/add-google-cloud-ops-agent-repo.sh
You would also need to remove the apt source of google-cloud-monitoring:
sudo rm /etc/apt/sources.list.d/google-cloud-monitoring.list
Then run the script installation inside the VM Instance:
sudo bash add-google-cloud-ops-agent-repo.sh --also-install
As the Legacy Monitoring Agent does not support the Debian 11 Bullseye.
Background:
I created a sandbox VM with VirtualBox on my macOS. It correctly spins up a VM (with CentOS7 running on it) on which I can access to.
Inside this sandbox vm, I want to spin up several vms in order to test Ansible Playbooks with Kitchen CI & Vagrant, thus I installed VirtualBox by downloading it from the following link: https://download.virtualbox.org/virtualbox/5.2.8/VirtualBox-5.2-5.2.8_121009_el7-1.x86_64.rpm
After the installation I executed the command:
[david#vmkitchen-env ansible-test]# VBoxManage --version
It returned:
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (3.10.0-693.2.1.el7.x86_64) or it
failed to load. Please recompile the kernel module and install it
by
sudo /sbin/vboxconfig
You will not be able to start VMs until this problem is fixed.
5.2.8r121009
I installed the Development tools, but I keep getting the same issue.
I don't think I need to recompile any kernel module. Any idea?
Thanks in advance for your help.
So, after searching on the internet, and not just on the VirtualBox website, I found the solution, and I was right: I did not need to compile any module.
The following is the reference to the CentOS wiki page:
https://wiki.centos.org/HowTos/Virtualization/VirtualBox
In a few words, I had to install dkms and kernel-devel packages. In order to do so, I needed to install EPEL repository; but personally I prefer to install and enable the IUS repository.
The following are the set of commands that worked for me:
yum groupinstall "Development tools"
yum install https://centos7.iuscommunity.org/ius-release.rpm
yum install dkms
yum install kernel-devel
reboot
After the machine had rebooted, I was able to get VirtualBox working fine.
I verified by the command line:
[david#vmkitchen-env ansible-test]# VBoxManage --version
And it returned the correct value:
5.2.8r121009
Below steps fixed the issue for me.
1.sudo /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
kernel-devel kernel-devel-3.10.0-957.10.1.el7.x86_64
2.This website has the kernel module - website
wget https://linuxsoft.cern.ch/cern/centos/7/updates/x86_64/Packages/kernel-devel-3.10.0-957.10.1.el7.x86_64.rpm
4.yum localinstall kernel-devel-3.10.0-957.10.1.el7.x86_64.rpm -y
5.sudo /sbin/vboxconfig
Issue resolved
On Fedora 36, I only had to run
sudo /sbin/vboxconfig
When I run ember test I got this
Could not start watchman
I can confirm that I have installed watchman, when I run which -a watchman, I got
/usr/local/bin/watchman
Am I missing something?
Fyi
ember -v return
ember-cli: 2.15.1
node: 8.6.0
os: linux x64
Try to reinstall watchman
$ git clone https://github.com/facebook/watchman.git
$ cd watchman
$ git checkout v4.9.0 # the latest stable release
$ ./autogen.sh
$ ./configure
$ make
$ sudo make install
More info here
Now, above process fails with error bser.cpp:345:17: error: offset of on non-standard-layout type 'json_object_t' in step make on macos, just upgraded to 10.15.6 catalina due to xcode upgrade issue, cmdline tools Apple clang version 12.0.0 (clang-1200.0.32.2)
Patching with these changes made it work to install watchman successfully tagedg v4.9.0
My company has firewall rules for yum so we can use only rpm to install the softwares on the RHEL 6 SERVER. So, I got a task to install virtualbox 5.1 on it. i used the rpm from the virtualbox website and installed it, but it failed with 2 dependencies and i installed them also. Then i got the below error.I just googled that i need some kernel-devel rpms but i dono, what to do after that and what else i need to make the virtual box running.
# virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (2.6.32-642.4.2.el6.x86_64) or it failed to load. Please recompile the kernel module and install it by
sudo /sbin/vboxconfig
You will not be able to start VMs until this problem is fixed.
Qt FATAL: QXcbConnection: Could not connect to display
Aborted
There will be lot of dependencies while installing rpm's. you need to check one by one and install the RPM's. Is suggest you to build local yum repository which doesnt require internet. you should use rhel 6 iso file to build local repo. And download the virtual box rpm, and try to install it with yum utility. yum will use local repo for dependency resolution.
Build repo:
1. mount DVD
[root#lh1 Packages]# cd /etc/yum.repos.d
[root#lh1 yum.repos.d]# vi dvd.repo
[root#lh1 yum.repos.d]# cat dvd.repo
[DVD_ISO]
name= Linux 6
baseurl=file:///mnt/cdrom
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY
gpgcheck=1
enabled=1
[root#lh1 rpm-gpg]# yum clean all
Loaded plugins: rhnplugin
[Errno 2] No such file or directory: '/var/cache/yum/x86_64/6Server'
[root#lh1 rpm-gpg]# yum repolist
Loaded plugins: rhnplugin
This system is not registered with ULN.
ULN support will be disabled.
DVD_ISO | 3.7 kB 00:00 ...
DVD_ISO/primary_db | 3.1 MB 00:00 ...
repo id repo name status
DVD_ISO Linux 6 3,379
repolist: 3,379
I get the below error message while I switch between my ember applications:
version: 2.4.2
Could not start watchman; falling back to NodeWatcher for file system events.
Visit ember-cli.com for more info.
Livereload server on http://localhost:49153
Could not serve on http://localhost:4200. It is either in use or you do not have permission.
Here are the packages that I have setup on my machine:
npm --version
2.14.20
bower --version
1.7.7
ember --version
2.4.2
node: 4.4.0
os: linux x64
Ember-cli (starting from release 0.1.3) requires watchman or some other service (e.g. NodeWatcher) for file watching.
You can find this info in the ember-cli release 0.1.3 changelog:
https://github.com/ember-cli/ember-cli/releases/tag/v0.1.3
Although I believe you could use your Ember app without watchman, could you confirm that you already have watchman installed?
If not, here's what works fine for me in Ubuntu 64bit:
// installing watchman from source
git clone https://github.com/facebook/watchman.git
cd watchman
./autogen.sh
./configure
make
sudo make install
if you still have problems after installing try also resetting your watchman configuration:
watchman watch-del-all
watchman watch-del /home/myproject // your project folder goes here...
watchman watch-project /home/myproject // your project folder goes
full installation instructions regarding watchman can also be found here
https://facebook.github.io/watchman/docs/install.html