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.

webgui will not stop array unRAID v4.7 after Firefly (mt-daapd addon)

Featured Replies

Hi all.

 

I wonder if anyone can help.

 

I have installed as an addon the Firefly mt-daapd package.

 

However I have an issue now where I cannot stop the array from the webgui, until the mt-daapd processes are stopped.

webgui simply shows

 

"Stopping..."

 

continually, and the syslogs tell me that the disk which firefly is using cannot be unmounted

this is of course what I suspected.

 

By stopping Firefly in its own webgui first (or manually killing its process), The stop button in unRAID's gui functions normally.

 

I have weebotech's Powerdown script hooked into the power button, this all works ok since it is able to stop firefly first.

 

My question is this...

 

Is there a way of editing a file which the webgui uses to shutdown the array ?

I dont seem to be able to find any source files for emHTTP  is this because it is all just built into one file ?

 

Issuing the "/etc/rc.d/rc.unRAID stop" command from the console does shutdown the array cleanly.

 

I am simply trying to avoid the need to stop Firefly first (from its own webgui) before being able to stop the array from unRAID's webgui.

 

Does this make sense ? Can I explain it any simpler ?

 

I would like to be able to "hook" into the "STOP ARRAY" button on the webgui

 

I have attached a screen shot of the syslog from the console of my virtual test machine showing

the continual retrys to unmount the disk.

 

Once I have a solution I will then consider making the change to my live server (which is running headless)

 

Pete

 

 

 

 

Snap1.jpg.0fd477d3e65745afd5b687bd8b4cc9a6.jpg

Hi all.

 

I wonder if anyone can help.

 

I have installed as an addon the Firefly mt-daapd package.

 

However I have an issue now where I cannot stop the array from the webgui, until the mt-daapd processes are stopped.

webgui simply shows

 

"Stopping..."

 

continually, and the syslogs tell me that the disk which firefly is using cannot be unmounted

this is of course what I suspected.

 

By stopping Firefly in its own webgui first (or manually killing its process), The stop button in unRAID's gui functions normally.

 

I have weebotech's Powerdown script hooked into the power button, this all works ok since it is able to stop firefly first.

 

My question is this...

 

Is there a way of editing a file which the webgui uses to shutdown the array ?

I dont seem to be able to find any source files for emHTTP  is this because it is all just built into one file ?

 

Issuing the "/etc/rc.d/rc.unRAID stop" command from the console does shutdown the array cleanly.

 

I am simply trying to avoid the need to stop Firefly first (from its own webgui) before being able to stop the array from unRAID's webgui.

 

Does this make sense ? Can I explain it any simpler ?

 

I would like to be able to "hook" into the "STOP ARRAY" button on the webgui

 

I have attached a screen shot of the syslog from the console of my virtual test machine showing

the continual retrys to unmount the disk.

 

Once I have a solution I will then consider making the change to my live server (which is running headless)

 

Pete

I use an program I wrote for things similar to this: unraid_addon_control.sh

see here: http://lime-technology.com/forum/index.php?topic=5686.msg53271

  • 2 weeks later...
  • Author

Thanks for your reply Joe.

 

I am looking into this again now. I am a bit of a newbie however when it comes to linux etc.

 

So am finding it a little hard to grasp. I can understand basic commands and simple scripts but find some extremely confusing.

 

Have you edited rc.unRAID then to prevent it from stopping the array ?.  I am finding it a bit difficult to fully understand the full sequence of events.

 

Regards

 

Pete

 

 

Thanks for your reply Joe.

 

I am looking into this again now. I am a bit of a newbie however when it comes to linux etc.

 

So am finding it a little hard to grasp. I can understand basic commands and simple scripts but find some extremely confusing.

Google is your friend.

 

The detailed description is in this post in that thread:

http://lime-technology.com/forum/index.php?topic=5686.msg56731#msg56731

Have you edited rc.unRAID then to prevent it from stopping the array ?.

No  it is why my script has the "-u" option.
  I am finding it a bit difficult to fully understand the full sequence of events.
It is a finite state machine running an infinite loop, sleeping every 10 seconds to check if the array is starting, or stopping.  It purposely changes directory to one of your data disks to force unRAID to emit messages when it is attempting to stop the array.  Then, if it detects those messages in the last 50 lines of your syslog, loops to process all the rc.???? scripts in /etc/rc.d/unraid.d/ in turn.  I have one rc.???? script for each program I start/stop.

 

  • Author

Thanks for taking the time to reply Joe.  :)

 

Things are a little clearer now. I will try it out on my virtual machine when I get the chance

and let you know how I get on.

 

 

  • Author

Hello Joe.

 

Just been having a play with your scripts, and thought you would like to know

that I have my virtual system doing exactly what I want now.

 

auto starts Firefly after array start, and auto stops before array stop when clicked on from the webgui.

 

Brilliant, thanks very much.  8)

 

Pete

Hi Pete,

 

I thought I recognised that user name...  Long time, no see.

 

I also have Firefly on my unRAID box.  I must now have a read of the thread that Joe L pointed you to and see if I can also figure out how to kill it cleanly (I'll enjoy the challenge).  Up to now I've just been doing a killall mt-daapd from the command line; and using the same method for Twonky Media Server and for Hamachi.  It works, but your way would be preferable.

 

Hope all goes well,

 

Les.

  • Author

Hi Les

 

Yes we get about the forums don't we  :)

 

Funnily enough I have until recently still been using an old Buffalo linkstation for Firefly. But since I have been using unRAID and XBMC for nearly two years

thought maybe I had better have go with Firefly on it. It was one of your posts that pointed me in the right direction.

 

I run 2 instances on the box actually, for Classical and Popular Music Libraries. But always found it a bit of a pain to kill the processes manually before

I could stop the array.

 

I haven't implemented the code on my live box yet, but have tested it a lot on a virtualbox unraid machine.

 

Nice to hear from you again Les.

 

Regards

 

Pete

  • Author

Once I have the scripts perfected on my live box. I will post them on here

 

Pete

Only one instance of Firefly here, but I do sometimes run up to three instances of Twonky - different port numbers, different folders, etc. Just works.

 

Les.

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.