Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

System log file reports errors in graphql-api.log file.

Featured Replies

Looking for guidance.
My UNRAID 7.1.4 system log file recently started reporting errors in the graphql-api.log file:

image.png

This is noted at two different location in the system log file.

I've looked at the graphql-api.log file and do not know enough about the inner workings to decipher what is wrong.

The errors listed in the graphql-api log file indicate that the various state files in "/usr/local/emhttp/state/ cannot be accessed because the file path is invalid.

But when I go to the terminal I can navigate to this location and see all the various files.

I've searched the UNRAID forums and online for a solution but have not found a solution.

For what it's worth, despite these errors, my server seems to working normally without any obvious issues.

I've attached my diagnostic file.

I am hoping and would be appreciative if someone can take a look and point me in the right direction.

Thanks.

madservr-diagnostics-20251103-0958.zip

  • Community Expert

This is not an error, the log highlights in red anything that has the word error in the text, hence the color.

  • Author

JorgeB,

Thanks for the quick reply.

Are you say this is not an error and can be ignored?

I was seeking some insight as I don't understand what's happening and why.

My understanding:

System log is reporting that there are errors logged in graphql-api.log

When I look at the contents of grahpql-api.log I see multiple errors seemingly indicating the path to the state files is invalid.

As far as I know this was not happening before I upgraded to 7.1.0.

I upgraded to 7.1.4 and it still is happening.

Now, I am seeking to correct whatever is causing the listed errors in graphql-api.log before upgrading to 7.2.0.

  • Community Expert
9 hours ago, madmaster said:

Are you say this is not an error and can be ignored?

Yes

  • 2 weeks later...

Thanks. I was about to post question about this error as well.

I am glad this is nothing to be of concern.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.