fs.writeFile works on localhost but not production server

Question

I have a basic web app setup that has a file structure that resembles this:

WEB APP
 - data
   -year.txt

 - cron
   -write.js

One parent directory with two folders each containing a single file. The write.js file generates a bunch of data on the backend, JSON.stringifies that data and writes the string to the year.txt file located in the other folder. This is what it looks like in the write.js file:

try {
   fs.writeFile(__dirname + '/../data/year.txt', JSON.stringify(organizedData), () => {
      console.log('SUCCESS');
      res.status(200);
      res.send(null);
    });
} catch (e) {
      res.status(500);
      console.log(e);
      res.send(null);
}

All of this works fine on my LOCAL server, the write.js file updates the year.txt with the correct data. I'm just struggling to figure out why this wont work on my production server, which is hosted on Google Cloud App Engine. The part that really confuses me is when I check the logs on this production server I get the "SUCCESS" message, which means the fs.writeFile function isn't throwing any errors. I check the year.txt file url path, and nothing is added. I can't seem to figure this out, does it maybe have something to do with the file path in the writeFile function?

If none of these solutions have worked, (and if you can change the code and redeploy it to production) I would try showing this `__dirname + '/../data/year.txt'` and `JSON.stringify(organizedData)` using `console.log` right above `console.log('SUCCESS');`. You might find something unexpected in these variables. — Jeff Mergler, Jan 26 '22 at 16:49

jfriend00 · Accepted Answer · 2022-01-26T14:53:37.723

fs.writeFile() passes its errors to the callback as the first argument err (which you are not paying any attention to). So, the first thing for you to do is to log the actual error fs.writeFile() is getting. But, I would "guess" that it's a file permission error for the directory you're trying to write to in your hosting configuration.

fs.writeFile() does not communicate errors by throwing an exception. So, you need to catch errors like this:

   fs.writeFile(__dirname + '/../data/year.txt', JSON.stringify(organizedData), (err) => {
      if (err) {
          console.log(err);
          res.sendStatus(500);
      } else {
          console.log('SUCCESS');
          res.sendStatus(200);
   });

does it maybe have something to do with the file path in the writeFile function

Yes, probably. But logging the actual error will give you more info. You can also read some doc on your hosting configuration to find out where exactly you are allowed to write to from your server process.

Here's a reference from the Google Cloud app engine docs on writing data to files. It suggests you either write to the temp directory or you write to Google Cloud storage.

You are right. It is giving me a EROFS log on my production server. Thanks for the help! — awoldt, Jan 26 '22 at 14:18
@awoldt - See [this discussion](https://stackoverflow.com/questions/51308489/google-clould-functions-deploy-erofs-read-only-file-system). It sounds like for temporary file storage, you write to the temp file directory and for lasting storage, you write to google cloud storage (through their APIs). And, here's a reference from the Google [docs](https://cloud.google.com/appengine/docs/standard/nodejs/using-temp-files). — jfriend00, Jan 26 '22 at 14:41

score 0 · Answer 2 · answered Jan 26 '22 at 14:22

It's maybe related to file system read-write policy in your server environment, you need to verify is your node application have enough permission for writing file in that specific directory

logging the actual error will give you and me more info. You also need to read some documentation on your to find out where exactly you are allowed to write to from your server process.

fs.writeFile works on localhost but not production server

2 Answers2