Now I have another problem, not sure if the s3 plugin is cosing it... My parity drive is not being spun down like other drives, so my server doesn't go to sleep mode... If I spun it down via "spin down" button, everything works fine, but without it, my parity keeps spinning.

Now I have another problem, not sure if the s3 plugin is cosing it... My parity drive is not being spun down like other drives, so my server doesn't go to sleep mode... If I spun it down via "spin down" button, everything works fine, but without it, my parity keeps spinning.

 

What brand of drive is this, Seagate ?

 

No, my parity drive is WD RED 2 TB. Unfortunately problems with accessing the gui are repeating. Not every time, so it is hard to find under what condition it happens...

No, my parity drive is WD RED 2 TB. Unfortunately problems with accessing the gui are repeating. Not every time, so it is hard to find under what condition it happens...

 

Can you try the following:

 

Main -> Parity -> Parity Device Settings -> Apply

 

This will rewrite the settings for the parity drive and may resolve a none spin down issue.

 

And when you are accessing the GUI, you are sure your system didn't go into sleep mode before (once in sleep it won't answer).

I'm trying to access gui after sending the WOL magic packet to my server. I'm sure it is awaken because the fans start spinning and i can access my files using Total Commander but i can't access gui.

I'm trying to access gui after sending the WOL magic packet to my server. I'm sure it is awaken because the fans start spinning and i can access my files using Total Commander but i can't access gui.

 

Sometimes it takes a while for emhttp (web server) to answer - don't ask why, it is a unRAID design. Give it some more time and see if the GUI comes back ...

Heh, about an hour ago, I waked the server to add some new films and music, I've read your post (about pressing apply in parity setting) and I had to reboot the server because gui was unaccessible.

Heh, about an hour ago, I waked the server to add some new films and music, I've read your post (about pressing apply in parity setting) and I had to reboot the server because gui was unaccessible.

 

Next time (before you reboot) can you telnet into your system and do

 

lsof -i -n -P | grep emhttp

emhttp    3093  root    3u  IPv4  6100      0t0  TCP *:80 (LISTEN)

And check that emhttp is listening. If this process is not working correctly then you don't have a GUI...

 

emhttp    1901  root    3u  IPv4  5254      0t0  TCP *:80 (LISTEN)

emhttp    1901  root    5u  IPv4  36455      0t0  TCP 192.168.1.19:80->192.168.                             

 

I don't know if this makes any difference, but as you can see the pid number is different from the one after rebooting (3093). And I can't access gui of course...

emhttp    1901  root    3u  IPv4  5254      0t0  TCP *:80 (LISTEN)

emhttp    1901  root    5u  IPv4  36455      0t0  TCP 192.168.1.19:80->192.168.                             

 

I don't know if this makes any difference, but as you can see the pid number is different from the one after rebooting (3093). And I can't access gui of course...

 

The process identifier (pid) is dynamically assigned by the OS and will differ each time.

 

Your second line seems truncated, can you copy/paste the full line ?

emhttp    1901  root    3u  IPv4  5254      0t0  TCP *:80 (LISTEN)

emhttp    1901  root    5u  IPv4  36455      0t0  TCP 192.168.1.19:80->192.168.1.15:51655 (ESTABLISHED)

 

emhttp    1901  root    3u  IPv4  5254      0t0  TCP *:80 (LISTEN)

emhttp    1901  root    5u  IPv4  36455      0t0  TCP 192.168.1.19:80->192.168.1.15:51655 (ESTABLISHED)

 

It might take some MINUTES for emhttp to respond, did you wait long enough / have enough patience

 

With the status above it should work !

I'm patient. I'm waiting from the moment I have written my previous post. And I can access my files but still can't access gui... Last time I was waiting over an hour...

An HOUR that is more than patience ...

 

You can do a simple test to see if emhttp is doing anything.

 

Close your browser which has the page open to your unRAID system, doing so will close the TCP session. You should see the second line with 'established' disappear.

I am also using sleep mode and don't have this problem, not sure if it is hardware related ...

ok, so I've made another reboot...

 

Now I have open window in my firefox and I can manage uRaid with gui... and if i paste following line in telenet:

 

lsof -i -n -P | grep emhttp

 

i got only one line of answerer:

 

emhttp    1899  root    3u  IPv4  5250      0t0  TCP *:80 (LISTEN)

 

when I access my files using TC I'v got second:

 

emhttp    1899  root    5u  IPv4  24364      0t0  TCP 192.168.1.19:80->192.168.1.15:55032 (ESTABLISHED)

 

Perhaps you could send me previous version (2.0.1) of S3 plugin? Everything was working fine with it...

I've decided to try reinstal all your plugins, so i deleted everything and installed once again Dynamix webGui. Next I tried to install Dynamix Plugin Control but when i type into telenet:

 

installplg dynamix.plugin.control-2.0.2-noarch-bergware.plg

 

I've got following error:

 

installing plugin: dynamix.plugin.control-2.0.2-noarch-bergware

 

Warning: simplexml_load_file(): I/O warning : failed to load external entity "dynamix.plugin.control-2.0.2-noarch-bergware.plg" in /usr/local/sbin/installplg on line 13

xml parse error

 

 

 

There is a new Problem with your plugin in version 2.0.3:

Since these update, when all disks running, its not possible to check the checkbox

on the Right side of the sleep button.

I must spin down all disks first, then the checkbox is klickable. After

This, all disk spin up again and the server goes to sleep.

Please can you correcht this because its an unnessesary spindown/spinup/spindown for the HDDs

 

Thanks

Zoni

I've got following error:

 

installing plugin: dynamix.plugin.control-2.0.2-noarch-bergware

 

Warning: simplexml_load_file(): I/O warning : failed to load external entity "dynamix.plugin.control-2.0.2-noarch-bergware.plg" in /usr/local/sbin/installplg on line 13

xml parse error

 

This error comes from installplg, and happens

 

(1) it couldn't find the indicated PLG file, e.g. it is in a different folder, it should be in /boot/config/plugins

 

(2) the contents of the PLG file is corrupted. Did you follow the correct procedure to download the PLG file otherwise github adds a lot of html coding to it.

 

There is a new Problem with your plugin in version 2.0.3:

Since these update, when all disks running, its not possible to check the checkbox

on the Right side of the sleep button.

I must spin down all disks first, then the checkbox is klickable. After

This, all disk spin up again and the server goes to sleep.

Please can you correcht this because its an unnessesary spindown/spinup/spindown for the HDDs

 

Thanks

Zoni

 

You are talking about the sleep button, right ?

 

This error comes from installplg, and happens

 

(1) it couldn't find the indicated PLG file, e.g. it is in a different folder, it should be in /boot/config/plugins

 

(2) the contents of the PLG file is corrupted. Did you follow the correct procedure to download the PLG file otherwise github adds a lot of html coding to it.

 

I downloaded it again and it works (plugin control). Unfortunately my main problem still isn't solved: i can't access gui after waking my server from sleep mode. Could you please send me previous (2.0.1) version of S3Sleep plugin?

[i downloaded it again and it works (plugin control). Unfortunately my main problem still isn't solved: i can't access gui after waking my server from sleep mode. Could you please send me previous (2.0.1) version of S3Sleep plugin?

 

The old version is still on github. You can download the PLG file (right-click and choose 'save link as').

 

Do a manual installation (please stop the service first before installing)

 

cd /boot/config/plugins

installplg dynamix.s3.sleep-2.0.1-noarch-bergware.plg

 

I installed the version 2.0.1 and... everything is working like a charm

I think I'll stick to this version

I installed the version 2.0.1 and... everything is working like a charm

I think I'll stick to this version

 

You just gave me some work to do 

@bonienl

Hmm... If 2.0.1 works, it must be related to my changes that it stopped working. If followed the thread closely, but I don't see were I could have gone so wrong, that it would stop the webgui from responding?!

 

On my system it works fine. If you need any assistence in finding the problem, feel free to contact me any time.