madmaster

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.

Looking for guidance. My UNRAID 7.1.4 system log file recently started reporting errors in the graphql-api.log file: 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

Thanks for the reply. I'm not sure I'm able to disable the AST2500. The MB manual lists it as the primary graphics controller for the VGA out port on the MB which is the only video out on the MB. And I use the AST2500 BMC controller functionality to remotely manage the server. So i don't want to disable it if that means losing the BMC functionality. I've tried using a dummy VGA adaptor and see no difference, I eventually get the Unexpected DP dual mode adaptor errors. You imply there is a way to "hide" the messages going to the syslog. How is this done? Does this mean the system would be silently creating these recurring errors but not writing them to the syslog? What I don't understand is why the server works for days or sometimes even weeks before the error messages start. And after they do start, why do they repeat every few seconds / minutes? This seems like a software bug of some sort. But I'm a LINUX / UNRAID beginner so it easily could be somethings wrong with my config. If the software warned me once or twice, but moved on it would be easier to ignore. And despite the error messages as far as I can tell I never experience a loss of functionality.

Question Regarding Intel-GPU-Top. Looking for some assistance or insight into recurring syslog error on my Unraid server. I'm a Linux and Unraid newbie and have been unable to solve a repeating system log error noted below. My system is an Asrock Rack E3C256d4U MB with Xeon E-2276G CPU. The MB has an AST2500 BMC and I have successfully (or so I thought) configured the MB and Plex to enable use of the intel iGPU for hardware transcoding. Worked great. Starting with version 6.11.1 and now on 6.11.5 I get the following error messages repeating every few seconds / minutes filling up the syslog file: To load the I915 intel driver, I have nothing in the "go" file and and have Intel_GPU_TOP plugin loaded. System devices shows both the AST2500 and intel UHD 630 graphics devices recognized and available. The MB has one onboard VGA output. I run headless on my home network without a dummy plug. At some random time after boot; sometimes within a few hours, sometimes much longer; up to 17 days, the above error messages start hitting the syslog file. They repeat every few seconds to every few minutes. Once they start they do not stop. The only way I can get them to temporarily stop is by rebooting the server. Despite the error messages, the server remains functional. I can log in and out, use Plex with or without hardware transcoding. To date, I've been unable to recognize a pattern of what may be causing the error messages or "force" the error to occur. IAny help or insight to get me pointed in the right direction of what I should investigate, including where to post this issue if this is not the correct place would be appreciated. Attached is my syslog and system diagnostics files if anyone is willing to take a look. madservr-syslog-20230502-1546.zip madservr-diagnostics-20230502-1048.zip

Hoping to get some assistance or insight into recurring syslog error on my Unraid server. I've posted about this previously and have received no replies or feedback. I'm a Linux and Unraid newbie and hope to get some insight or guidance on what may be going on. My system is an Asrock Rack E3C256d4U MB with Xeon E-2276G CPU. Use it on my home network to store backups and also have a Linuxserverio Plex docker. The MB has an AST2500 BMC and I have successfully (or so I thought) configured the MB and Plex to enable use of the intel iGPU for hardware transcoding. Worked great. Starting with version 6.11.1 and now on 6.11.5 I get the following error messages repeating every few seconds / minutes filling up the syslog file: To load the I915 intel driver, I have nothing in the "go" file and and have Intel_GPU_TOP plugin loaded. System devices shows both the AST2500 and intel UHD 630 graphics devices recognized and available. The MB has one onboard VGA output. I run headless on my home network without a dummy plug. At some random time after boot; sometimes within a few hours, sometimes much longer; up to 17 days, the error messages start hitting the syslog file. They repeat every few seconds to every few minutes. Once they start they do not stop. I've tried stopping the Plex docker; the error messages keep coming. I assume it's the i915 driver that is creating the messages. I don't understand what the message indicates. I have no DP adaptor attached. And why do they continually repeat instead of just getting one error message and moving on? The only way I can get them to temporarily stop is by rebooting the server. Despite the error messages, the server remains functional. I can log in and out, use Plex with or without hardware transcoding. I've searched the web to no avail. Doesn't seem to be a common problem as I've only seen one other post about the same errors; also unanswered. To be honest, when I read posts about graphics issues that dive into the inner workings of the kernal and/or the i915 driver module, I'm not able to understand enough to know if what I'm looking at might be my problem or a potential solution. To date, I've been unable to recognize a pattern of what may be causing the error messages or "force" the error to occur. The error messages just eventually start happening at some seemingly random time after boot. Any help or insight to get me pointed in the right direction of what I should investigate, including where to post this issue if this is not the correct place would be appreciated. Attached is my syslog and system diagnostics files if anyone is willing to take a look. madservr-syslog-20230502-1546.zipmadservr-syslog-20230502-1546.zip madservr-syslog-20230502-1546.zip madservr-diagnostics-20230502-1048.zip

Note sure if this is the correct place to post or not ... I am experiencing a persistent, recurring problem with Unraid running 6.11.5. After some random time, ranging from a few hours after boot to several days after boot I get repeating errors filling the system log file. The errors repeat,every few seconds to every few minutes, and once they start hitting the log, they do not stop. Below is a snip of the repeating errors: I'm running running 6.11.5 on a ASROCK E3C246D4U with a XEON E-2176G I don't have a lot running on the server. I use it for backup storage and I have a PLEX docker. My PLEX docker is configured to use the iGPU for transcoding and I have the i915 driver loaded. I was concerned the errors might indicate a hardware problem of some sort. Memory passed multiple passes of memtest86+. Everything lese seems to runs fine, even after the errors start hitting the system log, including PLEX with hardware transcoding active. I've been unable to solve this for more than 2 months and looking for some guidance / suggestion on resolving the issue. As far as I know, this behavior started after upgrading to 6.11.5. madmaster madservr-diagnostics-20230305-2243.zip