1 2 3 Previous Next 34 Replies Latest reply: Oct 17, 2011 3:13 PM by john_s@intel RSS

Intel ss-4200e four drive failure  please help needed

waheeb Community Member
Currently Being Moderated

I have an Intel ss-4200e and suddnly the four drive lights flash continously, I checked most discussions in this site and nothing solved my problem, any help will be very much appreciated.

 

the information as follows:

- I start with disk no 1 and change it with a new one , the device build data on it  I chk the status using the following command:

# mdadm --detail /dev/md0

 

Results :

# mdadm --detail /dev/md0
/dev/md0:
        Version : 00.90.03
  Creation Time : Sat May 14 13:11:10 2011
     Raid Level : raid5
     Array Size : 2930279808 (2794.53 GiB 3000.61 GB)
  Used Dev Size : 976759936 (931.51 GiB 1000.20 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Wed Oct 12 18:58:44 2011
          State : clean, degraded, recovering
Active Devices : 3
Working Devices : 4
Failed Devices : 0
  Spare Devices : 1

         Layout : left-asymmetric
     Chunk Size : 32K

Rebuild Status : 57% complete

           UUID : b4bf5a35:14da99dc:a7085406:b235cacd
         Events : 0.26

    Number   Major   Minor   RaidDevice State
       4     254        0        0      spare rebuilding   /dev/evms/.nodes/sda1
       1     254        1        1      active sync   /dev/evms/.nodes/sdb1
       2     254        2        2      active sync   /dev/evms/.nodes/sdc1
       3     254        3        3      active sync   /dev/evms/.nodes/sdd1
#

 

after finishing the building of HD and restarting the device I get the same status four lights flash continously again.

 

any help how to work it out , I have a very important data on the device related to many years.

  • 1. Re: Intel ss-4200e four drive failure  please help needed
    john_s@intel Community Member
    Currently Being Moderated

    Waheeb,

     

    What method did you use to determine that specifically disk 1 was bad?

     

    Regards,

    John

  • 2. Re: Intel ss-4200e four drive failure  please help needed
    waheeb Community Member
    Currently Being Moderated

    John,

     

    I was thinking that if I replace the hard disks one by one I will come up with a full duplicate of the 4 disks, so then I can try fixing the situation, so I started with disk No. 1, unfortunately I was very wrong about that and I discarded this Idea, actually all hard disk are excellent (I expect??).

     

    Regards

    Waheeb

  • 3. Re: Intel ss-4200e four drive failure  please help needed
    waheeb Community Member
    Currently Being Moderated

    John,

     

    The current device info as follows:

     

    ps
      PID  Uid        VSZ Stat Command
        1 root       1108 S   init
        2 root            SWN [ksoftirqd/0]
        3 root            SW< [events/0]
        4 root            SW< [khelper]
        5 root            SW< [kthread]
       34 root            SW< [kblockd/0]
       35 root            SW< [kacpid]
      132 root            SW< [kseriod]
      155 root            SW  [pdflush]
      156 root            SW  [pdflush]
      157 root            SW< [kswapd0]
      158 root            SW< [aio/0]
      290 root            SW< [krfcommd]
      310 root            SW< [loop0]
      314 root            SW< [loop1]
      326 root            SW< [loop2]
      369 root            SW< [ata/0]
      370 root            SW< [ata_aux]
      378 root            SW< [scsi_eh_0]
      379 root            SW< [scsi_eh_1]
      380 root            SW< [scsi_eh_2]
      381 root            SW< [scsi_eh_3]
      458 root            SW< [ksuspend_usbd]
      465 root            SW< [khubd]
      602 root            SW< [scsi_eh_4]
      603 root            SW< [scsi_eh_5]
      837 root        708 S   /sbin/netplugd -c /usr/local/netplug/netplugd.conf -F
      899 nobody      944 S   /usr/sbin/mdnsd
      912 root       2104 S   /bin/hostnamed
      914 root       3024 S   /sbin/executord -c /usr/local/cfg/sohoConfig.xml
      922 root       2944 S N /usr/sbin/discoverd
      936 root       1104 S   /sbin/getty 38400 tty1
      943 root       1108 S   /sbin/getty -L ttyS0 115200 vt100
      944 root       1100 S   /sbin/syslogd -n -m 0
      945 root       1104 S   /sbin/klogd -n
      946 root       1124 S   /bin/sh /usr/bin/sohoAudit
      947 root       1088 S   /usr/sbin/upnpd -webdir /etc/upnpd/web
      948 root       1088 S   /usr/sbin/upnpd -webdir /etc/upnpd/web
      950 nobody      940 S   /usr/sbin/mdnsd -debug
      951 root       1088 S   /usr/sbin/upnpd -webdir /etc/upnpd/web
      954 root       1952 S   /usr/sbin/sshd -D
      955 root      11792 S < /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
      957 root       1104 S   /usr/sbin/crond -f
      958 root        704 S   /usr/sbin/acpid -c /usr/local/acpi/events -f
      959 root       1088 S   /usr/sbin/upnpd -webdir /etc/upnpd/web
      960 root       1088 S   /usr/sbin/upnpd -webdir /etc/upnpd/web
      961 root       1088 S   /usr/sbin/upnpd -webdir /etc/upnpd/web
      963 root       1088 S   /usr/sbin/upnpd -webdir /etc/upnpd/web
    1014 root       1100 S   /bin/sh /usr/bin/Scavenger
    1019 root       1088 S   /usr/sbin/upnpd -webdir /etc/upnpd/web
    1021 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1022 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1023 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1024 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1025 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1026 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1027 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1065 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1066 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1067 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1068 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1070 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1155 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1156 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1157 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1163 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1217 root            SW< [md0_raid5]
    1260 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1286 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1287 root       1980 S   e2fsck -C 1 -y /dev/evms/md0vol1
    1940 root      11792 S < /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1941 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1954 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1955 root      11792 S   /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    3791 root       4620 S   sshd: root@pts/0
    3793 root       1108 S   -sh
    3878 root       1096 S   sleep 10
    3882 root       1100 S   sleep 5
    3886 root       1104 R   ps
    7610 root       1144 S   /usr/libexec/postfix/master
    7611 postfix    1240 S   qmgr -l -t fifo -u
    #

     

     

    # mdadm --detail /dev/md0
    /dev/md0:
            Version : 00.90.03
      Creation Time : Sat May 14 13:11:10 2011
         Raid Level : raid5
         Array Size : 2930279808 (2794.53 GiB 3000.61 GB)
      Used Dev Size : 976759936 (931.51 GiB 1000.20 GB)
       Raid Devices : 4
      Total Devices : 4
    Preferred Minor : 0
        Persistence : Superblock is persistent

        Update Time : Thu Oct 13 15:52:55 2011
              State : clean
    Active Devices : 4
    Working Devices : 4
    Failed Devices : 0
      Spare Devices : 0

             Layout : left-asymmetric
         Chunk Size : 32K

               UUID : b4bf5a35:14da99dc:a7085406:b235cacd
             Events : 0.42

        Number   Major   Minor   RaidDevice State
           0     254        0        0      active sync   /dev/evms/.nodes/sda1
           1     254        1        1      active sync   /dev/evms/.nodes/sdb1
           2     254        2        2      active sync   /dev/evms/.nodes/sdc1
           3     254        3        3      active sync   /dev/evms/.nodes/sdd1
    #

     

    Regards

    Waheeb

  • 4. Re: Intel ss-4200e four drive failure  please help needed
    john_s@intel Community Member
    Currently Being Moderated

    Whaeeb,

     

    One thing to note on your mdadm --detail /dev/md0 command is the creation time of Sat May 14 13:11:10 2011. Is that approximatrely when you put the system into service?

     

    What color were the LEDs flashing originally? All flashing purple (actually a combination of blue and amber) could indicate that the array was rebuilding, or recovering as your original post indicates. How long did you let the flashing LEDs go before you swapped disk 1? With the four disks you were running a RAID 5 array. You know that a two disk failure in a RAID 5 array is usually causes data destruction.

     

    It seems as though you're only using the command line access to investigate this, why? Were you able to connect to the storage system using the Intel Storage Manager application? If so, was there any indications of an issue there?

     

    You can see if your data is avialble from the command line. It can be found at the following path:
    /mnt/soho_storage/samba/shares
    There you'll find the Backups and public folders you see as shared folders when you access the device over the network.

     

    Let me know if you can navigate to the shared folders.

     

    Regards,

    John

  • 5. Re: Intel ss-4200e four drive failure  please help needed
    waheeb Community Member
    Currently Being Moderated

    John,

     

    thanks , you are right, in may 2011 I installed 4 new hard disks, this device worked for more than 3 years, in April 2011 the old hard disks start to have problems , so I copy everything to external medias, then in may, 2011  I install the new 4 (4 by 1TB - Hitachi H3D10003272S) hard disks and restore everything to device, then everything worked perfect  until Oct. 11, the time for the 4KVA ups maintenance , so I send the shut down order from the http link to the device, but device did not apply the shutdown command, so manually I press on the power button to make it shutdown.

    After finishing the maintenance of the UPS , I powered on the device and I get all the hard disks lights become amber with no flashing (before that date al lights was blue).

    So I change hard disk no. 1 as I explain in my previous post and the light start flashing blue and amber, I monitor the status of building the hard disk no. 1 by using SSH connection to device which I enable it previously using http://192.168.1.247/support.html, then when building become 100%, the device still flashing the same color with no activity on hard disk light on front panel of the device, I wait for more than 2 hours and lights still the same, so I send reboot command from the SSH connection, the result was all lights become amber again with no flashing

     

    Then I re installed the original hard disk no. 1 , the process of rebuilding starts again, and the rebuilding completed but all light still flashing amber and blue, this time I did not shut down the device and I am waiting, it is now more than 16 hours flashing .....I am still waiting..

     

    I am using the SSH connection and manual command because I can't access the device shares in network, even the  Storage Manager application only allow me to see the setting but shares or users not enabled , when  checking on hard disks status (Setting menu) it shows that all 4 hard disks failed, and this situation made me use the SSH connection - using ZOC/Pro 6.33 software.

     

    you ask me if I can access /mnt/soho_storage/samba/shares , actually I don't know how to do that , can you help me what command line I should use? I can't access the device by network (\\192.168.1.247)

     

    Regards

    Waheeb

  • 6. Re: Intel ss-4200e four drive failure  please help needed
    john_s@intel Community Member
    Currently Being Moderated

    Waheeb,

     

    Thanks for the information.

     

    I guess the easiest way would be to see if you've got an acquaintance that's proficient with Linux to help you with the standard commands. If that's not possible here we go.

     

    When you log into the system with SSH, you should be at the root directory (/). Just to be sure run the command to change the directory (cd) to the root:
    # cd /
    There run the cd command to navigate to the shares folder:
    # cd /mnt/soho_storage/samba/shares/
    There running the list command you should see the Backups and public folders as well as any user folders you have created
    # ls -al

    If you do see them, change directory to one of the directories that you have data in, such as:
    # cd /public/
    And list the contents there:
    ls -al

    If you get an error when you try to cd to the shares folder, try each step individually:
    # cd /mnt/
    # cd /soho_storage/
    # cd /samba/
    # cd /shares/
    And see if you can't get past a certain point.

     

    If you can't navigate to the shares folder this way, let's see if the md0 volume is mounted:
    # mount -v
    You should see a listing similar to this:
    rootfs on / type rootfs (rw)
    /dev/root.old on /initrd type ext2 (rw)
    none on / type tmpfs (rw)
    /dev/hda1 on /boot type ext2 (rw)
    /dev/loop0 on /mnt/apps type cramfs (ro)
    /dev/loop1 on /etc type ext2 (rw)
    /dev/loop2 on /oem type cramfs (ro)
    proc on /proc type proc (rw)
    none on /sys type sysfs (rw)
    devpts on /dev/pts type devpts (rw)
    none on /proc/bus/usb type usbfs (rw)
    /dev/evms/md/md0 on /mnt/soho_storage type ext3 (rw,noatime,data=ordered)

     

    The /dev/evms/md/md0 on /mnt/soho_storage type ext3 (rw,noatime,data=ordered) line is the mount of the data volume.

     

    If that doesn't show it gets a bit tricky.

     

    Let me know what you find.

     

    Regards,
    John

  • 7. Re: Intel ss-4200e four drive failure  please help needed
    waheeb Community Member
    Currently Being Moderated

    John,

     

    thank you for your help, this is the first time for me to work with linux, I spend the last 3 days try to learn about it, and I will continue.

    regarding the results here it is :

     

    [SSH] Logged in (password)

     

    BusyBox v1.8.2 (2008-06-24 04:41:38 MDT) built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    # cd /

    # ls -al
    drwxrwxrwt   13 root     root          420 Oct 13 17:42 .
    drwxrwxrwt   13 root     root          420 Oct 13 17:42 ..
    -rw-r--r--    1 root     root     38940672 Oct 13 12:41 .apps
    -rw-r--r--    1 root     root          163 Oct 14 16:54 .ash_history
    -rw-r--r--    1 root     root            0 Oct 13 12:41 .init_enable_core
    lrwxrwxrwx    1 root     root           13 Oct 13 12:41 bin -> /mnt/apps/bin
    drwxr-xr-x    6 root     root         1024 Mar 29  2008 boot
    drwxr-xr-x    7 root     root         6280 Oct 13 12:42 dev
    drwxr-xr-x   22 root     root         2048 Oct 13 12:42 etc
    -rw-r--r--    1 root     root            3 Oct 13 12:41 executord.pgid
    drwxr-xr-x    3 root     root           60 Oct 13 12:41 home
    drwxr-xr-x   10 admin    501          1024 Oct 13 12:41 initrd
    lrwxrwxrwx    1 root     root           13 Oct 13 12:41 lib -> /mnt/apps/lib
    drwxr-xr-x    4 root     root           80 Oct 13 12:41 mnt
    drwxr-xr-x    1 admin    244            20 Jan  1  1970 oem
    dr-xr-xr-x   95 root     root            0 Oct 13 12:41 proc
    lrwxrwxrwx    1 root     root           14 Oct 13 12:41 sbin -> /mnt/apps/sbin
    drwxr-xr-x   11 root     root            0 Oct 13 12:41 sys
    drwxrwxrwt    4 root     root          340 Oct 14 16:46 tmp
    lrwxrwxrwx    1 root     root           13 Oct 13 12:41 usr -> /mnt/apps/usr
    drwxr-xr-x    9 root     root          180 Oct 13 12:41 var

    # cd /mnt/soho_storage/shares/
    -sh: cd: can't cd to /mnt/soho_storage/shares/

    # cd /mnt/soho_storage/samba/shares/
    -sh: cd: can't cd to /mnt/soho_storage/samba/shares/

    # ls -al
    drwxrwxrwt   13 root     root          420 Oct 13 17:42 .
    drwxrwxrwt   13 root     root          420 Oct 13 17:42 ..
    -rw-r--r--    1 root     root     38940672 Oct 13 12:41 .apps
    -rw-r--r--    1 root     root          190 Oct 14 16:56 .ash_history
    -rw-r--r--    1 root     root            0 Oct 13 12:41 .init_enable_core
    lrwxrwxrwx    1 root     root           13 Oct 13 12:41 bin -> /mnt/apps/bin
    drwxr-xr-x    6 root     root         1024 Mar 29  2008 boot
    drwxr-xr-x    7 root     root         6280 Oct 13 12:42 dev
    drwxr-xr-x   22 root     root         2048 Oct 13 12:42 etc
    -rw-r--r--    1 root     root            3 Oct 13 12:41 executord.pgid
    drwxr-xr-x    3 root     root           60 Oct 13 12:41 home
    drwxr-xr-x   10 admin    501          1024 Oct 13 12:41 initrd
    lrwxrwxrwx    1 root     root           13 Oct 13 12:41 lib -> /mnt/apps/lib
    drwxr-xr-x    4 root     root           80 Oct 13 12:41 mnt
    drwxr-xr-x    1 admin    244            20 Jan  1  1970 oem
    dr-xr-xr-x   95 root     root            0 Oct 13 12:41 proc
    lrwxrwxrwx    1 root     root           14 Oct 13 12:41 sbin -> /mnt/apps/sbin
    drwxr-xr-x   11 root     root            0 Oct 13 12:41 sys
    drwxrwxrwt    4 root     root          340 Oct 14 16:46 tmp
    lrwxrwxrwx    1 root     root           13 Oct 13 12:41 usr -> /mnt/apps/usr
    drwxr-xr-x    9 root     root          180 Oct 13 12:41 var

    # cd /mnt/

    # ls -al
    drwxr-xr-x    4 root     root           80 Oct 13 12:41 .
    drwxrwxrwt   13 root     root          420 Oct 13 17:42 ..
    drwxr-xr-x    1 root     root           64 Jan  1  1970 apps
    drwxr-xr-x    4 root     root           80 Oct 13 12:45 soho_storage
    # cd /soho_storage/
    -sh: cd: can't cd to /soho_storage/

    #
    # mount -v
    rootfs on / type rootfs (rw)
    /dev/root.old on /initrd type ext2 (rw)
    none on / type tmpfs (rw)
    /dev/hda1 on /boot type ext2 (rw)
    /dev/loop0 on /mnt/apps type cramfs (ro)
    /dev/loop1 on /etc type ext2 (rw)
    /dev/loop2 on /oem type cramfs (ro)
    proc on /proc type proc (rw)
    none on /sys type sysfs (rw)
    devpts on /dev/pts type devpts (rw)
    none on /proc/bus/usb type usbfs (rw)
    #

     

     

    So please what to do next ...

     

    best regards

    Waheeb

  • 8. Re: Intel ss-4200e four drive failure  please help needed
    john_s@intel Community Member
    Currently Being Moderated

    Waheeb,

     

    Okay it looks like the md0vol1 volume isn't mounted for some reason.

     

    We can try some things to attempt data recovery and mounting the volume. These attempts may not be successful. Your data may not be available due to some condition that occurred. It's up to you if you feel comfortable in proceeding. Remember you're accessing the system with the highest access privileges and a mistake can cause irreparable damage.

     

    On every mount of the file system, the Storage System software does a file system check.  This will replay the data in the ext3 logs, correcting any file system issues that may have been caused by an improper shutdown.  If this fails a full file system check is performed.  The full check will make the file system mountable if possible.  It may also recover some user data that would otherwise be lost, and place it in the lost+found directory.  The lost+found directory is at /mnt/soho_storage/lost+found.  If the full file system check doesn't make the file system mountable, it is likely the user data is permanently lost.  However it may be desirable to attempt the file system check manually:

     

    e2fsck –f /dev/evms/md0vol1

     

    If this finishes successfully, attempt to mount the file system:

     

    mount /dev/evms/md0vol1 /mnt/soho_storage –t ext3

     

    If this succeeds the file system is now mounted.

     

    It’s possible that some user files were lost in the file system corruptions and recovered by the full file system check.  They would be placed in /mnt/soho_storage/lost+found.  If that is the case the data can be made available to the user by copying it to the public folder:

     

    cp –r /mnt/soho_storage/lost+found /mnt/soho_storage/samba/shares/public

     

    The files in lost+found may not be complete, or may be corrupted, but if successful you should have access to some or all of your data.

     

    The Storage System device should now be rebooted to restart all services. You should be able to navigate to the /shares/ folder as outlined earlier from here.

     

    If this doesn't resolve the issue we're out of options.

     

    Good Luck,
    John

  • 9. Re: Intel ss-4200e four drive failure  please help needed
    waheeb Community Member
    Currently Being Moderated

    John,

     

    I will proceed with it.

     

    the following is the result of the first command, it seems not working?

     

    BusyBox v1.8.2 (2008-06-24 04:41:38 MDT) built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    # e2fsck –f /dev/evms/md0vol1
    Usage: e2fsck [-panyrcdfvstDFSV] [-b superblock] [-B blocksize]
                    [-I inode_buffer_blocks] [-P process_inode_size]
                    [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
                    [-E extended-options] device

    Emergency help:
    -p                   Automatic repair (no questions)
    -n                   Make no changes to the filesystem
    -y                   Assume "yes" to all questions
    -c                   Check for bad blocks and add them to the badblock list
    -f                   Force checking even if filesystem is marked clean
    -v                   Be verbose
    -b superblock        Use alternative superblock
    -B blocksize         Force blocksize when looking for superblock
    -j external_journal  Set location of the external journal
    -l bad_blocks_file   Add to badblocks list
    -L bad_blocks_file   Set badblocks list
    #

     

    Regards

    Waheeb

  • 10. Re: Intel ss-4200e four drive failure  please help needed
    john_s@intel Community Member
    Currently Being Moderated

    Waheeb,

     

    Let me do some further checking on my system here.

     

    What version of firmware are you running on your SS4200-E?

     

    John

  • 11. Re: Intel ss-4200e four drive failure  please help needed
    waheeb Community Member
    Currently Being Moderated

    John,

     

    Ok,

    wrm.gif

     

    Also you get access to my computer to work directly using logmein, the login information will be sent directly to your mail.

     

    Regards

    Waheeb

  • 12. Re: Intel ss-4200e four drive failure  please help needed
    john_s@intel Community Member
    Currently Being Moderated

    Waheeb,

     

    Are you cutting and pasting the command? I noticed that the dash preceding the "f" seemed different that the one I got if I typed it in (–f instead of -f, see the slight difference?). First try typing the command in:

     

    e2fsck -f /dev/evms/md0vol1

     

    If this finishes successfully attempt to mount the file system:

     

    mount /dev/evms/md0vol1 /mnt/soho_storage -t ext3

     

    If that doesn't work the instructions may be based on an earlier firmware version. The following worked on mine, but gave me a warning message that the filesystem was mounted.

     

    To attempt the file system check manually use:

    e2fsck -f /dev/evms/md0/md0

     

    If this finishes successfully, attempt to mount the file system:

    mount /dev/evms/md0/md0 /mnt/soho_storage -t ext3

     

    John

  • 13. Re: Intel ss-4200e four drive failure  please help needed
    waheeb Community Member
    Currently Being Moderated

    John,

     

    yes I am cutting and paste, the reslut for the first command as follows:

     

    # e2fsck -f /dev/evms/md0vol1
    e2fsck 1.40.2 (12-Jul-2007)
    e2fsck: Device or resource busy while trying to open /dev/evms/md0vol1
    Filesystem mounted or opened exclusively by another program?
    #

     

    Pls note that the 4 lights of hard disks are flasing Amber / Blue and completed almost 20 hours and still flashing.

     

    Regards

    Waheeb

  • 14. Re: Intel ss-4200e four drive failure  please help needed
    waheeb Community Member
    Currently Being Moderated

    John,

     

    note the following: (using command # top)

     

    Mem: 147840K used, 360648K free, 0K shrd, 14916K buff, 110168K cached
    CPU:   0% usr   0% sys   0% nice 100% idle   0% io   0% irq   0% softirq
    Load average: 0.18 0.14 0.09
      PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
    1940  1021 root     S <  11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1955  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
      955   914 root     S <  11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1954  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1163  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1157  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1941  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1070  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1066  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1023  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1068  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1026  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1155  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1021   955 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1286  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1024  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1025  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1067  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1027  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1065  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1156  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1022  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    1260  1021 root     S    11800   2%   0% /usr/sbin/appweb -r /usr/local/appweb -f appweb.conf
    5811   954 root     S     4616   1%   0% sshd: root@pts/0
      914     1 root     S     3024   1%   0% /sbin/executord -c /usr/local/cfg/sohoConfig.xml
      922   914 root     S N   2944   1%   0% /usr/sbin/discoverd
      912     1 root     S     2104   0%   0% /bin/hostnamed
    1287  1157 root     S     1980   0%   0% e2fsck -C 1 -y /dev/evms/md0vol1
      954   914 root     S     1952   0%   0% /usr/sbin/sshd -D
    7611  7610 postfix  S     1240   0%   0% qmgr -l -t fifo -u
    7610     1 root     S     1144   0%   0% /usr/libexec/postfix/master
    4905   948 root     S     1124   0%   0% /usr/sbin/upnpd -webdir /etc/upnpd/web
      961   948 root     S     1124   0%   0% /usr/sbin/upnpd -webdir /etc/upnpd/web
    32651   948 root     S     1124   0%   0% /usr/sbin/upnpd -webdir /etc/upnpd/web
      946     1 root     S     1124   0%   0% /bin/sh /usr/bin/sohoAudit
      963   948 root     S     1124   0%   0% /usr/sbin/upnpd -webdir /etc/upnpd/web
      951   948 root     S     1124   0%   0% /usr/sbin/upnpd -webdir /etc/upnpd/web
      948   947 root     S     1124   0%   0% /usr/sbin/upnpd -webdir /etc/upnpd/web
    1019   948 root     S     1124   0%   0% /usr/sbin/upnpd -webdir /etc/upnpd/web
      947   914 root     S     1124   0%   0% /usr/sbin/upnpd -webdir /etc/upnpd/web
    5814  5811 root     S     1112   0%   0% -sh
        1     0 root     S     1108   0%   0% init
    18519  5814 root     R     1108   0%   0% top
      943     1 root     S     1108   0%   0% /sbin/getty -L ttyS0 115200 vt100
      936     1 root     S     1104   0%   0% /sbin/getty 38400 tty1
      957   914 root     S     1104   0%   0% /usr/sbin/crond -f
      945     1 root     S     1104   0%   0% /sbin/klogd -n
    1014   914 root     S     1100   0%   0% /bin/sh /usr/bin/Scavenger
      944     1 root     S     1100   0%   0% /sbin/syslogd -n -m 0
    18529  1014 root     S     1100   0%   0% sleep 5
    18534   946 root     S     1096   0%   0% sleep 10
      899     1 nobody   S      944   0%   0% /usr/sbin/mdnsd
      950   914 nobody   S      940   0%   0% /usr/sbin/mdnsd -debug

     

    Regards

    Waheeb

1 2 3 Previous Next

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points