{"id":4472,"date":"2016-06-17T02:31:25","date_gmt":"2016-06-17T02:31:25","guid":{"rendered":"http:\/\/www.garysieling.com\/blog\/?p=4472"},"modified":"2016-06-17T02:31:25","modified_gmt":"2016-06-17T02:31:25","slug":"fixing-node-error-emfile-many-open-files","status":"publish","type":"post","link":"https:\/\/www.garysieling.com\/blog\/fixing-node-error-emfile-many-open-files\/","title":{"rendered":"Fixing node error “EMFILE: too many open files”"},"content":{"rendered":"

I’ve found that sometimes when I write scripts in Node, I get errors like this:<\/p>\n

\nLoading info: Error: EMFILE: too many open files, \nopen 'D:\\projects\\image-annotation\\data\\youtube\\videos\\ZX8MBBohX3s.info.json'\n<\/pre>\n
Typically this is caused by invalid uses of “readFile” or “writeFile”, like so:<\/p>\n
\nwriteFile(\"json\/1\/\" + itemNumber + \".json\", \n  JSON.stringify(result, null, 2),            \n  (err) => {\n    if(err) {\n     return console.log(err);\n    }\n});\n<\/pre>\n
The reason that this doesn’t work is that the call is asynchronous – you’re supposed to provide a callback for success, and close the file there. <\/p>\n
If you don’t want to do this, you can easily fix this by using the “sync” methods:<\/p>\n
\nwriteFileSync(\"json\/1\/\" + itemNumber + \".json\", \n     JSON.stringify(result, null, 2));\n<\/pre>\n
In this case you don’t need the error handler, because errors will be thrown.<\/p>\n","protected":false},"excerpt":{"rendered":"
Fixing a “too many open files” error in Node<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[4],"tags":[302],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t