ShangHangin Posted April 14, 2012 Share Posted April 14, 2012 I have been having issues with the 5.0b14 webGUI. When I restarted my system, the GUI was not accessible. On the terminal I have on the server, I had a series of errors like this: PHP Notice: Undefined index: Icon in user/local/emhttp/plugins/webGUI/template.php on line 128 all there PHP Notice pointing at the template.php file, not only icon, but Title, etc. as well as different lines in the template.php file I tried to restart the webGUI - see command line below: root@HAL_9000:/# killall emhttp root@HAL_9000:/# nohup /user/local/sbin/emhttp & [1] 8014 root@HAL_9000:/# nohup: ignoring input and appending output to `nohup.out' nohup: failed to run command `/user/local/sbin/emhttp': No such file or directory [1]+ Exit 127 nohup /user/local/sbin/emhttp root@HAL_9000:/# Syslog log below root@HAL_9000:~# tail -f /var/log/syslog Apr 14 11:27:25 HAL_9000 unmenu-status: Starting unmenu web-server Apr 14 11:28:23 HAL_9000 emhttp: unRAID System Management Utility version 5.0-beta14 Apr 14 11:28:23 HAL_9000 emhttp: Copyright © 2005-2011, Lime Technology, LLC Apr 14 11:28:23 HAL_9000 emhttp: Pro key detected, GUID:xxxx Apr 14 11:28:23 HAL_9000 emhttp: rdevName.22 not found Apr 14 11:28:23 HAL_9000 emhttp: diskFsStatus.1 not found Apr 14 11:28:23 HAL_9000 kernel: emhttp[5680]: segfault at 0 ip b754f760 sp bfb21270 error 4 in libc-2.11.1.so[b74d6000+15c000] Apr 14 11:31:53 HAL_9000 in.telnetd[6237]: connect from 192.168.11.10 (192.168.11.10) Apr 14 11:31:54 HAL_9000 login[6238]: invalid password for 'UNKNOWN' on '/dev/pts/1' from '192.168.11.10' Apr 14 11:31:56 HAL_9000 login[6238]: ROOT LOGIN on '/dev/pts/1' from '192.168.11.10' Apr 14 11:45:05 HAL_9000 login[3728]: ROOT LOGIN on '/dev/tty1' Apr 14 11:45:52 HAL_9000 unmenu-status: Starting unmenu web-server Apr 14 11:46:48 HAL_9000 emhttp: unRAID System Management Utility version 5.0-beta14 Apr 14 11:46:48 HAL_9000 emhttp: Copyright © 2005-2011, Lime Technology, LLC Apr 14 11:46:48 HAL_9000 emhttp: Pro key detected, GUID: Apr 14 11:46:48 HAL_9000 emhttp: rdevName.22 not found Apr 14 11:46:48 HAL_9000 emhttp: diskFsStatus.1 not found Apr 14 11:46:48 HAL_9000 kernel: emhttp[8234]: segfault at 0 ip b764a760 sp bfa82ba0 error 4 in libc-2.11.1.so[b75d1000+15c000] attached s the full syslog. Aside from restarting, which has not seemed to help, any advice? syslog-2012-04-14-2.txt Quote Link to comment
dgaschk Posted April 14, 2012 Share Posted April 14, 2012 Run check disk on the Flash in a PC or Mac. Quote Link to comment
ShangHangin Posted April 14, 2012 Author Share Posted April 14, 2012 Did that, had some orphaned clusters - repairs. GUI works OK, but seems a bit intermittent. Still getting the same series of messages on my terminal even though the GUI is working. Is there a way to reload the code for it? Quote Link to comment
dgaschk Posted April 15, 2012 Share Posted April 15, 2012 Backup the flash. Then format and reinstall. Copy the key file from the backup. Quote Link to comment
gbdesai Posted April 18, 2012 Share Posted April 18, 2012 You have /user/local/sbin/emhttp vs. /usr/local/sbin/emhttp - that's at least why you get the error.. Quote Link to comment
ShangHangin Posted April 19, 2012 Author Share Posted April 19, 2012 Yes, it that case I posted, I did type the wrong directory. But even drilling into the directory, I still get a Segmentation fault. root@HAL_9000:/usr/local/sbin# emhttp Segmentation fault root@HAL_9000:/usr/local/sbin# Now - here is a very stupid question, as I have no Linux experience. Were does the /usr directory live? Is it on a disk or in virtual memory. Seems I could just recopy the file if it lived in on a physical disk. (Guess I will have to reformat the flash). Quote Link to comment
ShangHangin Posted April 20, 2012 Author Share Posted April 20, 2012 I have reformatted my USB, started clean with a 5.0b14 - still the same issue; The webGUI hangs, and then I can not get it back. Again, I ran the following to restart: root@HAL_9000:~# killall emhttp root@HAL_9000:~# nohup /usr/local/sbin/emhttp & [1] 6930 root@HAL_9000:~# nohup: ignoring input and appending output to `nohup.out' [1]+ Segmentation fault nohup /usr/local/sbin/emhttp root@HAL_9000:~# A bit of the syslog Apr 20 19:24:44 HAL_9000 unmenu-status: Starting unmenu web-server Apr 20 19:25:11 HAL_9000 vsftpd[6291]: connect from 192.168.11.1 (192.168.11.1) (Routine) Apr 20 19:27:07 HAL_9000 emhttp: unRAID System Management Utility version 5.0-beta14 (Lime Tech) Apr 20 19:27:07 HAL_9000 emhttp: Copyright © 2005-2011, Lime Technology, LLC (Lime Tech) Apr 20 19:27:07 HAL_9000 emhttp: Pro key detected, GUID: 054C-05B8-2211-108174003136 (Other emhttp) Apr 20 19:27:07 HAL_9000 emhttp: get_config_idx: fopen /boot/config/flash.cfg: No such file or directory - assigning defaults (Other emhttp) Apr 20 19:27:07 HAL_9000 emhttp: rdevName.22 not found (Other emhttp) Apr 20 19:27:07 HAL_9000 emhttp: diskFsStatus.1 not found (Other emhttp) Apr 20 19:27:07 HAL_9000 kernel: emhttp[6861]: segfault at 0 ip b748a760 sp bf9fde40 error 4 in libc-2.11.1.so[b7411000+15c000] (Errors) Apr 20 19:28:55 HAL_9000 vsftpd[6928]: connect from 192.168.11.1 (192.168.11.1) (Routine) Apr 20 19:28:55 HAL_9000 emhttp: unRAID System Management Utility version 5.0-beta14 (Lime Tech) Apr 20 19:28:55 HAL_9000 emhttp: Copyright © 2005-2011, Lime Technology, LLC (Lime Tech) Apr 20 19:28:55 HAL_9000 emhttp: Pro key detected, GUID: 054C-05B8-2211-108174003136 (Other emhttp) Apr 20 19:28:55 HAL_9000 emhttp: get_config_idx: fopen /boot/config/flash.cfg: No such file or directory - assigning defaults (Other emhttp) Apr 20 19:28:55 HAL_9000 emhttp: rdevName.22 not found (Other emhttp) Apr 20 19:28:55 HAL_9000 emhttp: diskFsStatus.1 not found (Other emhttp) Apr 20 19:28:55 HAL_9000 kernel: emhttp[6930]: segfault at 0 ip b74a1760 sp bfcf88b0 error 4 in libc-2.11.1.so[b7428000+15c000] (Errors) Apr 20 19:29:51 HAL_9000 vsftpd[6942]: connect from 192.168.11.1 (192.168.11.1) (Routine) The menu is stopped, but will not restart. Any other ideas?? Thanks, syslog-2012-04-20.txt.zip Quote Link to comment
ajax3712 Posted April 23, 2012 Share Posted April 23, 2012 Just took a quick scan of your syslog. There's a few lines of possible concern: Apr 20 19:09:06 HAL_9000 kernel: read_file: error 2 opening /boot/config/super.dat Apr 20 19:09:06 HAL_9000 kernel: md: could not read superblock from /boot/config/super.dat Apr 20 19:09:06 HAL_9000 kernel: md: initializing superblock Do these lines persist through restarts? Although I would definitely defer to a more knowledgeable unRAIDer (like Joe L. or other forum admin), I would say take a look at the following forum post (dealing with 5.0b2, but probably still applicable...) http://lime-technology.com/forum/index.php?topic=9438.0 Quote Link to comment
ShangHangin Posted May 2, 2012 Author Share Posted May 2, 2012 ... Note that I have NOT addressed any issue with webGui appearing to "hang" - if you let it sit long enough, it seems to come back. I realize this is not ideal and will address in rc3. For now I want to know if LSI chipset issues are solved and Realtek NIC's still work If so, I'll release as "official" -rc2, and then work on the webGui issues. http://lime-technology.com/forum/index.php?topic=19819.0 Since I have adopted patience and waited for the GUI to come back rather then reloading, I have had no issues. From Tom's comment in the 5.0rc1 thread above, GUI performance is a known issue. Will continue using 5.0b14 until rc2 or later are released. I will mark as resolved for the moderators. Lesson learned: Have patience, good things come to those who wait! SH Quote Link to comment
mbryanr Posted July 4, 2012 Share Posted July 4, 2012 Against better judgement, I restarted emhttp < inaccessible during a parity check> and got the same seg faults, corresponding syslog errors. Scared the crap out of me when I saw the entries. Anyways, a reboot got me back up and running - and I won't command line a emhttp restart again. Quote Link to comment
Recommended Posts
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.