Hi all,
I have tried searching for an explination for why I have the process Httpd running 6 times but am finding no answer. I have come to the conclusion it is from Apache2??? Each instance of the process are using up about 9% of my memory.
I have never enabled SSH access, so I doubt anyone has been inside the NAS causing problems. I tried resetting the nas to factory defaults, but the process still exists 6 times.
Anyone have any thoughts?
Thanks,
Same thing here, I’m not sure if this is normal or not. It isnt causing a problem so I see no reason to dig further.
normalname wrote:
Hi all,
I have tried searching for an explination for why I have the process Httpd running 6 times but am finding no answer. I have come to the conclusion it is from Apache2??? Each instance of the process are using up about 9% of my memory.
I have never enabled SSH access, so I doubt anyone has been inside the NAS causing problems. I tried resetting the nas to factory defaults, but the process still exists 6 times.
Anyone have any thoughts?
Thanks,
I am on the previous firmware and so I don’t know if they changed the web server. They used to use lighttpd (lighty) as the web server and though apache was always part of the firmware, it was never used. So I am not sure if they started using Apache in the new firmware…maybe they are.
Does anyone with the latest firmware see any process called lighttpd-angel and/or lighttpd from the dashboard’s process viewer…or in the process list obtained by the ‘ps -ef’ command from SSH? It would change certain things for me drastically and I’d rather know, if I can, before doing the upgrade in the future.
And btw, in the old firmware there were always two lighttpd instances running (one was lighttpd-angel and the other lighttpd). From the behavior that I have seen, it seemed that the angel’s task was to respawn a new lighttpd instance if the regular lighttpd terminated for some reason. Thus you would always have the web server running. And in the previous firmware there are no httpd processes runing…just those two lighttpd instances.
Cybernut1 wrote:
normalname wrote:
Hi all,
I have tried searching for an explination for why I have the process Httpd running 6 times but am finding no answer. I have come to the conclusion it is from Apache2??? Each instance of the process are using up about 9% of my memory.
I have never enabled SSH access, so I doubt anyone has been inside the NAS causing problems. I tried resetting the nas to factory defaults, but the process still exists 6 times.
Anyone have any thoughts?
Thanks,
I am on the previous firmware and so I don’t know if they changed the web server. They used to use lighttpd (lighty) as the web server and though apache was always part of the firmware, it was never used. So I am not sure if they started using Apache in the new firmware…maybe they are.
Does anyone with the latest firmware see any process called lighttpd-angel and/or lighttpd from the dashboard’s process viewer…or in the process list obtained by the ‘ps -ef’ command from SSH? It would change certain things for me drastically and I’d rather know, if I can, before doing the upgrade in the future.
And btw, in the old firmware there were always two lighttpd instances running (one was lighttpd-angel and the other lighttpd). From the behavior that I have seen, it seemed that the angel’s task was to respawn a new lighttpd instance if the regular lighttpd terminated for some reason. Thus you would always have the web server running. And in the previous firmware there are no httpd processes runing…just those two lighttpd instances.
Here ya go… Also, the lighttpd directory doesnt appear to have been touched during this upgrade.
~ # ps -ef
PID USER VSZ STAT COMMAND
1 root 2848 S init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
6 root 0 SW< [cpuset]
7 root 0 SW< [khelper]
8 root 0 SW [kdevtmpfs]
9 root 0 SW< [netns]
10 root 0 SW [kworker/u:1]
155 root 0 SW [sync_supers]
157 root 0 SW [bdi-default]
159 root 0 SW< [kblockd]
164 root 0 SW< [ata_sff]
175 root 0 SW [khubd]
178 root 0 SW< [md]
193 root 0 SW< [rpciod]
209 root 0 SW [kswapd0]
210 root 0 SW [fsnotify_mark]
211 root 0 SW< [nfsiod]
213 root 0 SW< [xfs_mru_cache]
214 root 0 SW< [xfslogd]
215 root 0 SW< [xfsdatad]
216 root 0 SW< [xfsconvertd]
217 root 0 SW< [crypto]
372 root 0 SW [scsi_eh_0]
375 root 0 SW [scsi_eh_1]
378 root 0 SW [kworker/u:2]
381 root 0 SW< [target_completi]
382 root 0 SW [LIO_rd_mcp]
392 root 0 SW [mtdblock0]
397 root 0 SW [mtdblock1]
402 root 0 SW [mtdblock2]
407 root 0 SW [mtdblock3]
412 root 0 SW [mtdblock4]
417 root 0 SW [mtdblock5]
422 root 0 SW [mtdblock6]
486 root 0 SW [flush-1:0]
513 root 0 SW [ubi_bgt0d]
518 root 0 SW [ubifs_bgt0_0]
2005 root 0 SW< [loop0]
2300 root 2848 S xmldb -n config
2303 root 2528 S xmldb -n config -s /var/run/xmldb_sock_wto
2355 root 0 SW [ubi_bgt1d]
2429 root 2432 S up_read_daemon
2430 root 2240 S up_send_daemon
2554 root 2752 S /usr/sbin/syslogd -r -m 0 --rt_line 800
2635 root 2336 S mserver
2649 root 14176 S mail_daemon
2735 root 0 SW [md0_raid1]
2755 root 0 SW [jbd2/sda4-8]
2756 root 0 SW< [ext4-dio-unwrit]
2761 root 0 SW [jbd2/sdb4-8]
2762 root 0 SW< [ext4-dio-unwrit]
2770 root 0 SW [md1_raid1]
2778 root 0 SW [jbd2/md1-8]
2781 root 0 SW< [ext4-dio-unwrit]
2811 messageb 3680 S /usr/bin/dbus-daemon --system
2814 root 4384 S avahi-daemon: running [OURCLOUD.local]
2823 root 5184 S /usr/sbin/sshd -f /etc/ssh/sshd_config
2838 root 2144 S lld2d egiga0
2932 root 4864 S fan_control 0 c
2934 root 4640 S set_pwm
2944 root 5792 S sysinfod
2958 root 2528 S xmldb -n config -s /var/run/xmldb_sock_sysinfo
3084 root 44800 S httpd -f /usr/local/apache2/conf/httpd.conf -k graceful
3089 root 4800 S /usr/bin/rotatelogs -n 2 /usr/local/apache2/logs/web_error.log 256K
3090 root 4800 S /usr/bin/rotatelogs -n 2 /usr/local/apache2/logs/web_access.log 256K
3091 root 4800 S /usr/bin/rotatelogs -n 2 /usr/local/apache2/logs/access.log 256K
3092 root 4800 S /usr/bin/rotatelogs -n 2 /usr/local/apache2/logs/access.log 256K
3095 root 4800 S /usr/bin/rotatelogs -n 2 /usr/local/apache2/logs/access.log 256K
3128 root 4928 S system_daemon
3130 root 4736 S chk_io
3203 root 7520 S N /usr/local/orion/communicationmanager/communicationmanager -f 120 -l 5
3226 root 2816 S xmldb -n config -s /var/run/xmldb_sock_vv
3234 root 2848 S init
3362 root 0 SW< [iscsi_eh]
3385 root 4800 S < iscsid -f
3425 root 2240 S /usr/local/twonky/twonkystarter -D -ip 192.168.5.50 -httpport 9000 -appdata /mnt/HD_a4/twonkymedia -logfile /mnt/HD_a4/twonkymedia/twonkymedia-log.txt
3427 root 40320 S /usr/local/twonky/twonkyserver -D -ip 192.168.5.50 -httpport 9000 -appdata /mnt/HD_a4/twonkymedia -logfile /mnt/HD_a4/twonkymedia/twonkymedia-log.txt
3557 root 2848 S {mysqld_safe} /bin/sh /usr/bin/mysqld_safe --user=root --datadir=/mnt/HD_a4/.@database@
3618 root 30208 S /usr/libexec/mysqld --basedir=/usr --datadir=/mnt/HD_a4/.@database@ --user=root --log-error=/mnt/HD_a4/.@database@/OURCLOUD.err --pid-file=/mnt/HD_a4/.@database@/OURCLOUD.pid
3664 root 70208 S upnp_nas_device -webdir /etc/upnp
3671 root 4000 S apkg
3769 root 33472 S /usr/local/wdmcserver/bin/wdmcserver -v /tmp/Volumes.xml
3788 root 41312 S /usr/local/wdmcserver/bin/wdphotodbmerger
3800 root 10688 S /usr/local/bin/wdnotifier
3942 root 34848 S smbd -D
3950 root 18624 S nmbd -D
4004 root 2048 S chk_blockip
4011 root 9600 S {pure-ftpd_s} pure-ftpd (SERVER)
4073 root 5824 S /usr/sbin/netatalk -F /etc/netatalk/afp.conf
4074 root 9216 S /usr/sbin/afpd -d -F /etc/netatalk/afp.conf
4075 root 5856 S /usr/sbin/cnid_metad -d -F /etc/netatalk/afp.conf
4086 root 0 SW [kworker/0:2]
4201 root 5344 S scheddler
4292 root 2528 S xmldb -n config -s /var/run/xmldb_sock_usbdev_info
4307 root 4352 S chk_hotplug
5447 root 2912 S N {openvpn} /bin/bash /usr/sbin/openvpn /usr/local/orion/openvpnclient/client.ovpn
5453 root 5408 S N /usr/sbin/openvpn.bin /usr/local/orion/openvpnclient/client.ovpn
8323 root 2976 S crond
8976 root 35200 S smbd -D
10423 root 46560 S httpd -f /usr/local/apache2/conf/httpd.conf -k graceful
11571 root 0 SW [kworker/0:1]
22206 root 47232 S httpd -f /usr/local/apache2/conf/httpd.conf -k graceful
28959 root 7584 S sshd: sshd@ttyp0
28982 root 3008 S -sh
29216 root 3008 R ps -ef
32422 root 47808 S httpd -f /usr/local/apache2/conf/httpd.conf -k graceful
~ #
Thanks a ton, Vertech1! So indeed they started using Apache webserver now. Interesting…very interesting. I always found it odd that they included it but weren’t using it. I am curious why they switched over. Possibly because Apache is more rigorously and frequently patched from a security standpoint…but on the flip side, lighty has a smaller memory footprint and is supposed to be nimbler in serving requests.
Thanks for the entire process list Vertech1…much appreciated.
EDIT: On reviewing the latest firmware’s source code, I realize that WD has not strayed from their past practice of including and using much older versons of web server software…that wasthe case with lighty and still is, now that they are using Apache. They are including Apache 2.2.24 in the new release, which was released on feb 25, 2013 (according to http://archive.apache.org/dist/httpd/ ) - so even older than the stale lighty version they were including. So no benefit of getting the latest pacthed Apache - and that must not have been why they switched to Apache. This Apache is not only not the latest version (which is 2.4.x) but it is an older version of Apache’s now legacy version. Sigh
Thanks for the info guys. Can’t say much of it made sense though! I’m very much not linux savvy.