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.

Intermittent Bus Error from Monitor

Featured Replies

Intermittently (on average once per day) I, and at least one other user are having the monitor process exit abnormally with a bus error.  This happens on both of my servers.  (Admittedly, they are both very similar in terms of CPU / Motherboard).  All memory tests pass with flying colours.

 

The applicable syslog line is 

Jun 7 15:45:01 Server_B crond[1689]: exit status 135 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

This results in an email being sent to root (since its an error from the cron daemon) of:

From: Server_B <[email protected]>
Date: Wed, Jun 7, 2017 at 3:45 PM
Subject: cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
To: root


/bin/sh: line 1: 31326 Bus error               /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

There is no leadup within the syslog to this issue (ie: nothing logged for an hour or so before or after regarding this).

 

 

Just to add, I'm having this same problem (as well as ACPI errors looking like they relate to IPMI, see my other topic).

 

/bin/sh: line 1: 18808 Bus error               /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

 

  • 1 month later...

Happening to me too - My server is crashing as well and I believe it is at this time - here are six messages from last night:

1.

cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

/bin/sh: line 1: 12938 Killed                  /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

2.
cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
/bin/sh: line 1: 13655 Killed                  /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

3.
cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
/bin/sh: line 1: 13928 Killed                  /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

4.
cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
/bin/sh: line 1: 14241 Killed                  /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

5.
cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
/bin/sh: line 1: 14617 Killed                  /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

6.
cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null


/bin/sh: line 1: 14938 Killed                  /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

All between 1:57am to 2:03 am

 

  • Author
1 hour ago, dstanley said:

Happening to me too - My server is crashing as well and I believe it is at this time - here are six messages from last night:

1.

cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

/bin/sh: line 1: 12938 Killed                  /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

2.
cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
/bin/sh: line 1: 13655 Killed                  /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

 

3.
cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
/bin/sh: line 1: 13928 Killed                  /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

 

4.
cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
/bin/sh: line 1: 14241 Killed                  /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

 

5.
cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null
/bin/sh: line 1: 14617 Killed                  /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

 

6.
cron for user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null


/bin/sh: line 1: 14938 Killed                  /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null

 

All between 1:57am to 2:03 am

 

Are you on the latest RC? (6)  I was seeing them on previous RC's, but haven't seen one in quite a while..

Yes - version 6.3.5

Although I am using version 6.3.5. unRAID DVB Edition (Digital Devices (Github) so that I can use my HS-PVRs in SageTV Docker.

  • Author
2 minutes ago, dstanley said:

Yes - version 6.3.5

Although I am using version 6.3.5. unRAID DVB Edition (Digital Devices (Github) so that I can use my HS-PVRs in SageTV Docker.

Ah.  This thread was about that error and 6.4  I would reboot and run a memtest for minimum one pass just to rule that out

DOH! - sorry!

I found this thread on a search and didn't read the forum group - will check the memory as suggested - thanks for all your work here Squid!

Archived

This topic is now archived and is closed to further replies.

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.