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.

Got a dead.letter today! user.script.start.hourly.sh Bus errors - custom bash script the culprit?

Featured Replies

I am investigating what happend today on my Unraid server, I'd appreciate anyone experienced helping me with this:

After realizing that nothing was respondig anymore in the GUI (or any docker service), I tried connecting via. ssh, which was extremely slow but worked somehow.

 

The only thing to get out was the "dead.letter" attached.

 

I don't really understand what caused the Bus errors running the /etc/cron.hourly/user.script.start.hourly.sh script
(which just executes /usr/local/emhttp/plugins/user.scripts/startSchedule.php)

 

First guess is simply, that the flash drive just died or a user script file is corrupted somehow?

My second guess is that there might be a problem with my mostly self-written user script that I recently updated.

 

What do I do: I backup my flash drive with a custom bash script using the User Scripts plugin.

A few days before I realized that, after upgrading Unraid apprently, the *-flash-backup-*.zip file generated by /usr/local/emhttp/webGui/scripts/flash_backup was stored in a different place now. So I updated the script - please see the script attaced! (... I added the cleanup function; introduced the $EMHTTP and $FLASH_BAK_DIR variable). The old version worked great for months...

 

After checking paths and stuff manually I ran the script once. The backup zip file was stored on my nfs drive and everything looked good. So I assumed It is working as intended again.

 

Now, I am not sure if this script may have deleted something that it is not supposed to? But I can't a bug in the bash script.

Also the script was scheduled weekly, not hourly or course.

 

I really appreciate anyone having an assumption about what could have happened, or finding a possible bug in my script.

 

I believe there are no logs that I am really able to read out now, right? I did use a flash backup and transfered the key to get my server up again.

Thanks!

 

 

Edit: After running the flash_backup script again, It seems now that the *-flash-backup-*.zip is again stored simply in '/' (like before)
I could swear It was stored in /mnt/user/system last week. Still there should not have been deleted anything else at this location running:

rm /mnt/user/system/*-flash-backup-*.zip - because the glob pattern is not mathing, right?

 

dead.letter backup_flash_nfs.sh

Edited by theuema

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.