April 27, 201313 yr I recently just had to rebuild a disk that had a write error detected. Now after the rebuild, the unraid web gui main page will not start. Unmenu works fine with TOWER:80 (but not with the IP directly...). The array is not started. I am using 5.0 rc12a The main page usually times out, but sometimes it goes through and only plain text appears and all images are broken. I am using the following: Simple Features Sabnzbd Couchpotato Sickbeard Plex Media Server Crashplan SQL Transmission My current memory looks like this: total used free shared buffers cached Mem: 3888404 1251312 2637092 0 2444 1205544 -/+ buffers/cache: 43324 3845080 Swap: 0 0 0 These commands do not fix the problem, even temporarily: killall emhttp nohup /usr/local/sbin/emhttp & My go script looks like this: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & /boot/unmenu/uu unraid_notify start cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c cp --preserve=timestamps /boot/custom/etc/ssh/ssh*key* /etc/ssh chmod 600 /etc/ssh/ssh*key* /etc/rc.d/rc.sshd start Also, the syslog is capturing TONS of events now. I see something like this repeating over and over: Apr 26 20:49:31 Tower emhttp: shcmd (375890): /usr/local/sbin/emhttp_event driver_loaded (System) Apr 26 20:49:31 Tower emhttp_event: driver_loaded (System) Apr 26 20:49:31 Tower emhttp: shcmd (375891): rmmod md-mod |$stuff$ logger (Other emhttp) Apr 26 20:49:31 Tower emhttp: shcmd (375892): modprobe md-mod super=/boot/config/super.dat slots=24 |$stuff$ logger (unRAID engine) Apr 26 20:49:31 Tower emhttp: shcmd (375893): udevadm settle (Other emhttp) Apr 26 20:49:31 Tower emhttp: Device inventory: (Drive related) Apr 26 20:49:31 Tower emhttp: ST4000DX000-1CL160_Z1Z04HT3 (sda) 3907018584 (Drive related) Apr 26 20:49:31 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA2705958 (sdb) 1953514584 (Drive related) Apr 26 20:49:31 Tower emhttp: ST4000DM000-1F2168_Z3002YFN (sdc) 3907018584 (Drive related) Apr 26 20:49:31 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA1271505 (sdd) 1953514584 (Drive related) Apr 26 20:49:31 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA1272500 (sde) 1953514584 (Drive related) Apr 26 20:49:31 Tower emhttp: ST3320620AS_6QF28RW3 (sdg) 312571224 (Drive related) Apr 26 20:49:31 Tower emhttp: ST31500341AS_9VS2ERBW (sdh) 1465138584 (Drive related) Apr 26 20:49:31 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA2794674 (sdi) 1953514584 (Drive related) Apr 26 20:49:31 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA2709486 (sdj) 1953514584 (Drive related) Apr 26 20:49:31 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA3256714 (sdk) 1953514584 (Drive related) Apr 26 20:49:31 Tower emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA3344693 (sdl) 1953514584 (Drive related) Apr 26 20:49:31 Tower kernel: md: unRAID driver removed (System) Apr 26 20:49:31 Tower kernel: md: unRAID driver 2.1.6 installed (System) Apr 26 20:49:31 Tower kernel: mdcmd (1): import 0 8,0 3907018532 ST4000DX000-1CL160_Z1Z04HT3 (unRAID engine) Apr 26 20:49:31 Tower kernel: md: import disk0: [8,0] (sda) ST4000DX000-1CL160_Z1Z04HT3 size: 3907018532 (Drive related) Apr 26 20:49:31 Tower kernel: mdcmd (2): import 1 8,32 3907018532 ST4000DM000-1F2168_Z3002YFN (unRAID engine) Apr 26 20:49:31 Tower kernel: md: import disk1: [8,32] (sdc) ST4000DM000-1F2168_Z3002YFN size: 3907018532 (Drive related) Apr 26 20:49:31 Tower kernel: mdcmd (3): import 2 8,16 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA2705958 (unRAID engine) Apr 26 20:49:31 Tower kernel: md: import disk2: [8,16] (sdb) WDC_WD20EARS-00MVWB0_WD-WMAZA2705958 size: 1953514552 (Drive related) Apr 26 20:49:31 Tower kernel: mdcmd (4): import 3 8,48 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA1271505 (unRAID engine) Apr 26 20:49:31 Tower kernel: md: import disk3: [8,48] (sdd) WDC_WD20EARS-00MVWB0_WD-WCAZA1271505 size: 1953514552 (Drive related) Apr 26 20:49:31 Tower kernel: mdcmd (5): import 4 8,64 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA1272500 (unRAID engine) Apr 26 20:49:31 Tower kernel: md: import disk4: [8,64] (sde) WDC_WD20EARS-00MVWB0_WD-WCAZA1272500 size: 1953514552 (Drive related) Apr 26 20:49:31 Tower kernel: mdcmd (6): import 5 8,176 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA3344693 (unRAID engine) Apr 26 20:49:31 Tower kernel: md: import disk5: [8,176] (sdl) WDC_WD20EARS-00MVWB0_WD-WMAZA3344693 size: 1953514552 (Drive related) Apr 26 20:49:31 Tower kernel: mdcmd (7): import 6 8,160 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA3256714 (unRAID engine) Apr 26 20:49:31 Tower kernel: md: import disk6: [8,160] (sdk) WDC_WD20EARS-00MVWB0_WD-WMAZA3256714 size: 1953514552 (Drive related) Apr 26 20:49:31 Tower kernel: mdcmd (: import 7 8,144 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA2709486 (unRAID engine) Apr 26 20:49:31 Tower kernel: md: import disk7: [8,144] (sdj) WDC_WD20EARS-00MVWB0_WD-WMAZA2709486 size: 1953514552 (Drive related) Apr 26 20:49:31 Tower kernel: mdcmd (9): import 8 8,128 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA2794674 (unRAID engine) Apr 26 20:49:31 Tower kernel: md: import disk8: [8,128] (sdi) WDC_WD20EARS-00MVWB0_WD-WMAZA2794674 size: 1953514552 (Drive related) Apr 26 20:49:31 Tower kernel: mdcmd (10): import 9 8,112 1465138552 ST31500341AS_9VS2ERBW (unRAID engine) Apr 26 20:49:31 Tower kernel: md: import disk9: [8,112] (sdh) ST31500341AS_9VS2ERBW size: 1465138552 (Drive related) Apr 26 20:49:31 Tower kernel: mdcmd (11): import 10 0,0 (unRAID engine) Apr 26 20:49:31 Tower kernel: mdcmd (12): import 11 0,0 (unRAID engine) Apr 26 20:49:31 Tower kernel: mdcmd (13): import 12 0,0 (unRAID engine) Apr 26 20:49:31 Tower kernel: mdcmd (14): import 13 0,0 (unRAID engine) Apr 26 20:49:31 Tower kernel: mdcmd (15): import 14 0,0 (unRAID engine) Apr 26 20:49:31 Tower kernel: mdcmd (16): import 15 0,0 (unRAID engine) Apr 26 20:49:31 Tower kernel: mdcmd (17): import 16 0,0 (unRAID engine) Apr 26 20:49:31 Tower kernel: mdcmd (18): import 17 0,0 (unRAID engine) Apr 26 20:49:31 Tower kernel: mdcmd (19): import 18 0,0 (unRAID engine) Apr 26 20:49:31 Tower kernel: mdcmd (20): import 19 0,0 (unRAID engine) Apr 26 20:49:31 Tower kernel: mdcmd (21): import 20 0,0 (unRAID engine) Apr 26 20:49:31 Tower kernel: mdcmd (22): import 21 0,0 (unRAID engine) Apr 26 20:49:31 Tower kernel: mdcmd (23): import 22 0,0 (unRAID engine) Apr 26 20:49:31 Tower kernel: mdcmd (24): import 23 0,0 (unRAID engine) Apr 26 20:49:31 Tower emhttp: shcmd (375894): /usr/local/sbin/emhttp_event driver_loaded (System) Apr 26 20:49:31 Tower emhttp_event: driver_loaded (System) Any idea what is going on here?
April 27, 201313 yr You can't restart emhttp in V5. unmenu is usually at tower:8080 not tower:80 If you can't get to it by IP then the IP must be wrong. Try to ping tower and see what you get. Maybe you have more than one computer on your network with the same IP. Can you telnet in? What does ifconfig show? Don't know about your syslog snippet but you should try to get your networking fixed first then if you still have a problem attach a complete syslog.
April 27, 201313 yr Author You are correct. tower:8080 loads unmenu fine but 192.168.2.100:8080 does not. I have a static reserved IP set for my unraid server and its never been a problem in the past. Rebooting all network devices doesn't do anything. Yes I can telnet in just fine and ifconfig shows: eth0 Link encap:Ethernet HWaddr 00:23:54:31:c4:7f inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:792671 errors:0 dropped:9 overruns:0 frame:0 TX packets:1354621 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:107157717 (102.1 MiB) TX bytes:656923010 (626.4 MiB) Interrupt:43 Base address:0x2000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1001 errors:0 dropped:0 overruns:0 frame:0 TX packets:1001 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:117502 (114.7 KiB) TX bytes:117502 (114.7 KiB) There are no conflicting IP addresses.
April 27, 201313 yr Author I got tower:8080 and 192.168.2.100:8080 to resolve correctly, but I am still having issues with the main webGUI. I find it really odd that it will sometimes load but with no images. It just sits there an churns.
April 27, 201313 yr Author After some searching it looks like the excessive logging (loading and unloading) happens when the array is not started and whenever the webGUI has actions. Here is the output from ps -ef > /boot/ps_output.txt UID PID PPID C STIME TTY TIME CMD root 1 0 0 23:21 ? 00:00:06 init root 2 0 0 23:21 ? 00:00:00 [kthreadd] root 3 2 0 23:21 ? 00:00:00 [ksoftirqd/0] root 4 2 0 23:21 ? 00:00:00 [kworker/0:0] root 6 2 0 23:21 ? 00:00:00 [migration/0] root 7 2 0 23:21 ? 00:00:00 [migration/1] root 9 2 0 23:21 ? 00:00:00 [ksoftirqd/1] root 10 2 0 23:21 ? 00:00:00 [kworker/0:1] root 11 2 0 23:21 ? 00:00:00 [khelper] root 12 2 0 23:21 ? 00:00:00 [kworker/u:1] root 158 2 0 23:21 ? 00:00:00 [sync_supers] root 160 2 0 23:21 ? 00:00:00 [bdi-default] root 162 2 0 23:21 ? 00:00:00 [kblockd] root 275 2 0 23:21 ? 00:00:00 [ata_sff] root 285 2 0 23:21 ? 00:00:00 [khubd] root 308 2 0 23:27 ? 00:00:00 [kworker/0:13] root 394 2 0 23:21 ? 00:00:00 [rpciod] root 414 2 0 23:21 ? 00:00:00 [kswapd0] root 475 2 0 23:21 ? 00:00:00 [fsnotify_mark] root 495 2 0 23:21 ? 00:00:00 [nfsiod] root 498 2 0 23:21 ? 00:00:00 [cifsiod] root 504 2 0 23:21 ? 00:00:00 [crypto] root 570 2 0 23:21 ? 00:00:00 [kworker/1:1] root 658 2 0 23:21 ? 00:00:00 [deferwq] root 659 2 0 23:21 ? 00:00:00 [kworker/1:2] root 686 1 0 23:21 ? 00:00:00 /sbin/udevd --daemon root 846 2 0 23:21 ? 00:00:00 [scsi_eh_0] root 857 2 0 23:21 ? 00:00:00 [scsi_eh_1] root 858 2 0 23:21 ? 00:00:00 [usb-storage] root 880 2 0 23:21 ? 00:00:00 [scsi_eh_2] root 881 2 0 23:21 ? 00:00:00 [scsi_eh_3] root 882 2 0 23:21 ? 00:00:00 [scsi_eh_4] root 883 2 0 23:21 ? 00:00:00 [scsi_eh_5] root 884 2 0 23:21 ? 00:00:00 [scsi_eh_6] root 885 2 0 23:21 ? 00:00:00 [scsi_eh_7] root 890 2 0 23:21 ? 00:00:00 [kworker/u:7] root 943 2 0 23:33 ? 00:00:00 [kworker/0:2] root 945 2 0 23:21 ? 00:00:00 [scsi_wq_0] root 961 686 0 23:21 ? 00:00:00 /sbin/udevd --daemon root 962 686 0 23:21 ? 00:00:00 /sbin/udevd --daemon root 1060 1 0 23:21 ? 00:00:01 /usr/sbin/syslogd -m0 root 1064 1 0 23:21 ? 00:00:00 /usr/sbin/klogd -c 3 -x bin 1106 1 0 23:21 ? 00:00:00 /sbin/rpc.portmap root 1110 1 0 23:21 ? 00:00:00 /sbin/rpc.statd root 1120 1 0 23:21 ? 00:00:00 /usr/sbin/inetd root 1127 1 0 23:21 ? 00:00:00 /usr/sbin/ntpd -g -p /var/run/ntpd.pid root 1134 1 0 23:21 ? 00:00:00 /usr/sbin/acpid 81 1144 1 0 23:21 ? 00:00:00 /usr/bin/dbus-daemon --system root 1149 1 0 23:21 ? 00:00:00 /usr/sbin/crond -l notice daemon 1151 1 0 23:21 ? 00:00:00 /usr/sbin/atd -b 15 -l 1 root 7256 1 3 23:23 ? 00:00:24 /usr/local/sbin/emhttp root 7270 2 0 23:23 ? 00:00:00 [kworker/0:3] root 7281 1 0 23:23 ? 00:00:00 /usr/sbin/sshd root 7284 1 0 23:23 tty1 00:00:00 /sbin/agetty 38400 tty1 linux root 7285 1 0 23:23 tty2 00:00:00 /sbin/agetty 38400 tty2 linux root 7286 1 0 23:23 tty3 00:00:00 /sbin/agetty 38400 tty3 linux root 7287 1 0 23:23 tty4 00:00:00 /sbin/agetty 38400 tty4 linux root 7288 1 0 23:23 tty5 00:00:00 /sbin/agetty 38400 tty5 linux root 7289 1 0 23:23 tty6 00:00:00 /sbin/agetty 38400 tty6 linux root 7290 686 0 23:23 ? 00:00:00 /sbin/udevd --daemon root 7311 1 0 23:23 ? 00:00:00 /usr/sbin/nmbd -D root 7313 1 0 23:23 ? 00:00:00 /usr/sbin/smbd -D root 7318 7313 0 23:23 ? 00:00:00 /usr/sbin/smbd -D root 7328 2 0 23:23 ? 00:00:00 [kworker/0:4] root 7403 2 0 23:23 ? 00:00:00 [kworker/0:6] root 7441 2 0 23:23 ? 00:00:00 [kworker/0:7] root 7479 2 0 23:23 ? 00:00:00 [kworker/0:8] root 7517 2 0 23:23 ? 00:00:00 [kworker/0:9] root 7555 2 0 23:23 ? 00:00:00 [kworker/0:10] root 7675 7826 0 23:34 ? 00:00:00 sleep 60 root 7826 1 0 23:22 ? 00:00:00 /bin/bash /usr/bin/unraid_notify run_service root 8082 2 0 23:23 ? 00:00:00 [kworker/1:4] root 8126 2 0 23:23 ? 00:00:00 [kworker/1:5] root 8181 2 0 23:23 ? 00:00:00 [kworker/1:6] root 8284 2 0 23:23 ? 00:00:00 [kworker/1:7] root 8436 2 0 23:23 ? 00:00:00 [kworker/0:11] root 9234 2 0 23:23 ? 00:00:00 [kworker/0:12] root 9642 2 0 23:23 ? 00:00:00 [kworker/1:9] root 9902 2 0 23:23 ? 00:00:00 [kworker/1:10] root 11029 2 0 23:35 ? 00:00:00 [md] root 11030 2 0 23:35 ? 00:00:00 [mdrecoveryd] root 11032 2 0 23:35 ? 00:00:00 [spinupd] root 11033 2 0 23:35 ? 00:00:00 [spinupd] root 11034 2 0 23:35 ? 00:00:00 [spinupd] root 11035 2 0 23:35 ? 00:00:00 [spinupd] root 11036 2 0 23:35 ? 00:00:00 [spinupd] root 11037 2 0 23:35 ? 00:00:00 [spinupd] root 11038 2 0 23:35 ? 00:00:00 [spinupd] root 11039 2 0 23:35 ? 00:00:00 [spinupd] root 11040 2 0 23:35 ? 00:00:00 [spinupd] root 11041 2 0 23:35 ? 00:00:00 [spinupd] root 11055 7256 0 23:35 ? 00:00:00 sh -c cd /usr/local/emhttp; /usr/bin/php -d magic_quotes_gpc=Off plugins/simpleFeatures/include/SystemTemp.php 'item=CPU&unit=C' root 11056 11055 0 23:35 ? 00:00:00 /usr/bin/php -d magic_quotes_gpc=Off plugins/simpleFeatures/include/SystemTemp.php item=CPU&unit=C root 11060 17616 0 23:35 pts/0 00:00:00 ps -ef root 12014 2 0 23:24 ? 00:00:00 [kworker/1:11] root 14240 2 0 23:30 ? 00:00:00 [kworker/1:3] root 15097 2 0 23:24 ? 00:00:00 [kworker/1:12] root 17020 7281 0 23:30 ? 00:00:00 sshd: root@pts/0 root 17616 17020 0 23:30 pts/0 00:00:00 -bash nobody 28171 7313 0 23:32 ? 00:00:00 /usr/sbin/smbd -D
April 27, 201313 yr Author SOLVED. Turns out I had the webgui open in a browser (Chrome) on another computer on the network. Once I closed that browser, all was well. Anyone know why this happened? This seems like it might be some kind of bug...
Archived
This topic is now archived and is closed to further replies.