Is This Software Raid 5 Status Ok?

I have researched RAID, RAID 5, and my conclusion is that the following RAID 5 Status listings show that the software RAID 5 (md4) is OK/good.
But I need at least a second opinion!

output from: 'cat /proc/mdstat'
md4 : active raid5 sdc1[0] sde1[3] sdd1[1]
1465143552 blocks super 1.0 level 5, 128k chunk, algorithm 2 [3/2] [UU_]
bitmap: 1/350 pages [4KB], 1024KB chunk

(NOTE: md0-3 are RAID 1 and certainly OK).
my concern here is '[3/2] [UU_]' above

output from: 'mdadm --detail /dev/md4'
/dev/md4:
Version : 01.00.03
Creation Time : Mon Mar 24 12:06:43 2008
Raid Level : raid5
Array Size : 1465143552 (1397.27 GiB 1500.31 GB)
Used Dev Size : 1465143552 (1397.27 GiB 1500.31 GB)
Raid Devices : 3
Total Devices : 3
Preferred Minor : 4
Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Tue Jun 3 13:30:13 2008
State : active, degraded
Active Devices : 2
Working Devices : 3
Failed Devices : 0
Spare Devices : 1

Layout : left-symmetric
Chunk Size : 128K

Name : 4
UUID : 14e8cb06:2fd235d1:362ac661:e1e4c384
Events : 9702

Number Major Minor RaidDevice State
0 8 33 0 active sync /dev/sdc1
1 8 49 1 active sync /dev/sdd1
3 8 65 2 spare rebuilding /dev/sde1

my concerns here are:
State : active, degraded

Number Major Minor RaidDevice State
3 8 65 2 spare rebuilding /dev/sde1

* NOTE: I searched system logs after 3 startup, run, and shutdown cycles and did or could not find the follwing matches in the log for md4:
'Disk failure' NOTHING Found
'resyncing' NOTHING Found
'disabling' Found 'kernel: JBD: barrier-based sync failed on md4 - disabling barriers' when the system starts up'

I thank you for your reviews and opinions!

One of the elements in the array is degraded, as the report says. You have to reincorporate it into the array.

Thank you, the status was NOT OK
to resolve this I did the follwing:
1) turned off quotas on /dev/sde via YaST->partitioner (could not remove sde1 from md4 because 'quotas' was still using drive)
2) removed md4/sde1 via 'mdadm /dev/md4 -r /dev/sde1'
3) added md4 sde1 back via 'mdadm /dev/md4 -a /dev/sde1'
NOTE:turning quotas back on for /dev/sde1 after addition worked

Outputs are now correct for RAID 5 '/dev/md4' !

cat /proc/mdstat
Personalities : [raid1] [raid0] [raid6] [raid5] [raid4]
md4 : active raid5 sdc1[0] sde1[3] sdd1[1]
1465143552 blocks super 1.0 level 5, 128k chunk, algorithm 2 [3/3] [UUU]
bitmap: 0/350 pages [0KB], 1024KB chunk

AND

mdadm --detail /dev/md4
/dev/md4:
Version : 01.00.03
Creation Time : Mon Mar 24 12:06:43 2008
Raid Level : raid5
Array Size : 1465143552 (1397.27 GiB 1500.31 GB)
Used Dev Size : 1465143552 (1397.27 GiB 1500.31 GB)
Raid Devices : 3
Total Devices : 3
Preferred Minor : 4
Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Thu Jun 5 21:38:57 2008
State : active
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 128K

Name : 4
UUID : 14e8cb06:2fd235d1:362ac661:e1e4c384
Events : 9814

Number Major Minor RaidDevice State
0 8 33 0 active sync /dev/sdc1
1 8 49 1 active sync /dev/sdd1
3 8 65 2 active sync /dev/sde1

NOW everything fixed OK with RAID 5 /dev/sde1
Thank you for your help!