Failed to use on mint Linux :(
See original GitHub issueWhen I use the ReLaXed on mint linux 18.3 after all npm dependencies have been installed,it throws an error
Watching 11.pug and its directory tree.
events.js:167
throw er; // Unhandled 'error' event
^
Error: ENOSPC: no space left on device, watch '/home/yue/pdf2web/ReLaXed/node_modules/ajv/lib/dotjs/README.md'
at FSWatcher.start (fs.js:1389:26)
at Object.fs.watch (fs.js:1426:11)
at createFsWatchInstance (/usr/lib/node_modules/relaxedjs/node_modules/chokidar/lib/nodefs-handler.js:37:15)
at setFsWatchListener (/usr/lib/node_modules/relaxedjs/node_modules/chokidar/lib/nodefs-handler.js:80:15)
at FSWatcher.NodeFsHandler._watchWithNodeFs (/usr/lib/node_modules/relaxedjs/node_modules/chokidar/lib/nodefs-handler.js:229:14)
at FSWatcher.NodeFsHandler._handleFile (/usr/lib/node_modules/relaxedjs/node_modules/chokidar/lib/nodefs-handler.js:256:21)
at FSWatcher.<anonymous> (/usr/lib/node_modules/relaxedjs/node_modules/chokidar/lib/nodefs-handler.js:474:21)
at FSReqWrap.oncomplete (fs.js:166:5)
Emitted 'error' event at:
at FSWatcher._handleError (/usr/lib/node_modules/relaxedjs/node_modules/chokidar/index.js:260:10)
at createFsWatchInstance (/usr/lib/node_modules/relaxedjs/node_modules/chokidar/lib/nodefs-handler.js:39:5)
at setFsWatchListener (/usr/lib/node_modules/relaxedjs/node_modules/chokidar/lib/nodefs-handler.js:80:15)
[... lines matching original stack trace ...]
at FSReqWrap.oncomplete (fs.js:166:5)
But when I use the command df -h
,I found that my system still has a lot of space。
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 18M 1.6G 2% /run
/dev/sdb4 189G 17G 163G 10% /
tmpfs 7.8G 37M 7.8G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup
/dev/sda1 99M 48M 52M 48% /boot/efi
/dev/sdb5 115G 16G 94G 15% /home
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 1.6G 40K 1.6G 1% /run/user/1000
After that,I updatemax_user_watches
to solve the same problem from https://stackoverflow.com/questions/22475849/node-js-error-enospc.However,It did not solve the problem.And the ReLaXed Into an endless wait, did not return success or error。
➜ pdf2web relaxed 11.pug
Watching 11.pug and its directory tree.
I also try to run ReLaXed with root privileges,but it still no change in the above situation.On the other hand,I has ensured the correct chromium version has been downloaded and configured correctly in index.js. 😦 I don’t have any ideas so I hope to turn to you
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
On Mint 21, several services fail - Linux Mint Forums
Re: On Mint 21, several services fail I compared my service situation, on Mint 21, with a PC running Mint 20.3. (That latter...
Read more >[SOLVED] Linux install fails EVERY TIME! Help! [SOLVED]
I have tried Ubuntu, Elementary, MX Linux, etc. Each and every one of the installs gets to 95% and fails at the grub-install...
Read more >installation or removal of software failed [linux mint 20.3, and ...
You can try this command and see if it works. Code: Select all sudo dpkg --configure -a. Post what ever error it gives...
Read more >Failed to install software using command [solved]
sudo apt-get install master-pdf-editor-5.4.38-qt5-all.amd64.deb. After displaying a series of error messages, installation fails and aborts.
Read more >Mint 20.2 Installing Apps failure. - Linux Mint Forums
I'm a rank beginner with Linux but highly experienced with Windows. ... This error could be caused by required additional software packages which ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is the expected behaviour. It is watching the directory and will render when a file changes in the directory. If you want to build directly, from v0.1.4 (released yesterday) use option --build-once at the end of your command
There is no reason to be sorry. Any feedback is welcome and helpful like @Zulko already wrote.