Hello,

 

I am new to Unraid. Have a Pro key. Installed unMenu 1.3 and it was working fine. I recently added a cache drive (the only change to the system) and I can't access unMenu. I am not sure if the web server is crashing or something else. In the browser I go to tower:8080 and browser just hangs in waiting for response mode.  I can still go back to standard GUI after a little while. Sometimes, main unMenu screen comes back but I can't access any of the features.  The only thing I see in the logs is this:

 

Jan 13 14:07:54 Tower unmenu[1469]: awk: ./unmenu.awk:630: fatal: print to "/inet/tcp/8080/0/0" failed (Connection reset by peer)

Jan 13 14:07:54 Tower unmenu-status: Exiting unmenu web-server, exit status code = 2

Jan 13 14:07:54 Tower unmenu[1469]: unmenu.awk unable to open port.  It  may already be running

Jan 13 14:08:04 Tower unmenu-status: Starting unmenu web-server

root@Tower:~#

 

 

Any thoughts?

 

Those messages would indicate it is already running and you are trying to invoke it again, or something else you installed already has port 8080 in use.

 

Joe L.

Thanks Joe for quick response.

 

That is what I thought but what I pretty much do is reboot the server, and try to access unmenu via tower:8080. In my Go script I got very basic stuff:

 

#!/bin/bash

# Start the Management Utility

/usr/local/sbin/emhttp &

echo "guest_enable=NO" >> /etc/vsftpd.conf

/boot/unmenu/uu

 

I did not install any other packages or add-ons. Again the only thing I did was cache drive (which I would not think would have anything to do with this)

 

Is there anything I can look at? 

Well, something had port 8080 open.

 

Yes you can stop the array and reboot.  But before you do, do you think it might be interesting to look in your system log? or do you already know everything in it looks perfectly normal?

 

Easiest, use the "Check for Updates" button and Install Updates" button on the user-scripts page.  Also, use the "Restart unMENU" button.

 

One last thing, unMENU is only able to handle one request at a time.  If you invoke a page that takes minutes to return, all other pages will time out if you attempt them.  Be patient.

 

Joe L.

Ok I see what the issue is. You right. I was missing something, Patience.  UnMenu actually works but browser response is longer then I had few weeks back when I used it. Port 8080 error was when I was trying to refresh I guess.

 

I timed browser response as I navigate thru unMenu and its about 2.5min for some of the features. I did have better response before, but I had less drives as well. I do have total of 4 + parity + cache.  2.5 min feels a bit slow to me. I tried Disk Usage and its been running for almost 10 min and it still did not comeback. I only have 80% on disk 1 (2T) out of the whole array. Is that typical for unMenu?

 

Thanks

Ok I see what the issue is. You right. I was missing something, Patience.  UnMenu actually works but browser response is longer then I had few weeks back when I used it. Port 8080 error was when I was trying to refresh I guess.

 

I timed browser response as I navigate thru unMenu and its about 2.5min for some of the features. I did have better response before, but I had less drives as well. I do have total of 4 + parity + cache.  2.5 min feels a bit slow to me. I tried Disk Usage and its been running for almost 10 min and it still did not comeback. I only have 80% on disk 1 (2T) out of the whole array. Is that typical for unMenu?

 

Thanks

 

Not typical, so there may be something else going on with your setup.

 

Post a complete syslog for use to take a look through along with your complete hardware specs.

 

Just for grins and giggles also restart unRAID and possibly your router.

Ok I see what the issue is. You right. I was missing something, Patience.  UnMenu actually works but browser response is longer then I had few weeks back when I used it. Port 8080 error was when I was trying to refresh I guess.

 

I timed browser response as I navigate thru unMenu and its about 2.5min for some of the features. I did have better response before, but I had less drives as well. I do have total of 4 + parity + cache.  2.5 min feels a bit slow to me. I tried Disk Usage and its been running for almost 10 min and it still did not comeback. I only have 80% on disk 1 (2T) out of the whole array. Is that typical for unMenu?

 

Thanks

No, it takes a while, but probably something else is going on on your server.

 

Joe L.

 

Not typical, so there may be something else going on with your setup.

 

Post a complete syslog for use to take a look through along with your complete hardware specs.

 

Just for grins and giggles also restart unRAID and possibly your router.

Attached is a log from a freshly rebooted system.

unraid_log.txt

Attached is a log from a freshly rebooted system.

To start, two of your disks are in PIO mode  That would make access very slow.

 

Jan 13 16:42:24 Tower kernel: hde: WDC WD1200JB-00GVA0, ATA DISK drive

Jan 13 16:42:24 Tower kernel: hdf: ST3300620A, ATA DISK drive

Jan 13 16:42:24 Tower kernel: hde: host max PIO4 wanted PIO255(auto-tune) selected PIO4

Jan 13 16:42:24 Tower kernel: hde: UDMA/100 mode selected

Jan 13 16:42:24 Tower kernel: hdf: host max PIO4 wanted PIO255(auto-tune) selected PIO4

Jan 13 16:42:24 Tower kernel: hdf: UDMA/100 mode selected

 

Are you using IDE drives?  If so, are you using a flat 80 conductor IDE cable?

hmm that is the cache drive I added. Second IDE is connected but not assigned into an array. I had this older IDE drive figured it should be enough for a cache drive. Drive jumpers are in CableSelect and I do use flat cable. Drive came up in PIO 4, which is probably it fastest it can support anyway. So you saying an older IDE drive can slow down the system access like that?  BTW I want to thank for such a quick response.

 

Thanks

SOrry. I just doublecheck the cable.. it is a 40 pin

That was it.. THANK YOU. I got to say, great response. You guys are great. Again thanks for the help.

SOrry. I just doublecheck the cable.. it is a 40 pin

They are all 40 pin, but the one that can be used a high speeds are 80 conductor.  The 40 conductor cables are used for CD drives and very old PCs that had slower smaller disks that did not support DMA mode.

 

Glad you are up and running at the faster speed.

For future reference, this command will tell you what is running on a port (and the pid so you can kill it)

 

lsof -i:<port>

 

eg: lsof -i:8080