Discuss

discuss@lists.centos.org

34753 discussions

SELInux conflict with Postfixadmin
by Robert Moskowitz 21 Feb '17

21 Feb '17

postfixadmin setup.php is claiming: *Error: Smarty template compile directory templates_c is not writable.* *Please make it writable.* *If you are using SELinux or AppArmor, you might need to adjust their setup to allow write access.* This goes away with 'setenforce 0', so it is an SELinux issue. I have tried both: restorecon -Rv /usr/share/postfixadmin and chcon -R -t httpd_sys_content_t /usr/share/postfixadmin and they are not the problem. Googling this message doe snot produce any SELinux advice. Any ideas? thanks

3 5

movie player vs. mp3
by Michael Hennebry 21 Feb '17

21 Feb '17

I have movie player installed on centos 6. When I try to play an mp3 file, it complains about the lack of a codec, mpeg-1 something 3. google hasn't helped. What package do I need? Trying to install ffmpeg gets me a no such package message. I've dealt with codec issues before. Mostly what I remember is that before I was done, I wanted to kill something. -- Michael hennebry(a)web.cs.ndsu.NoDak.edu "Sorry but your password must contain an uppercase letter, a number, a haiku, a gang sign, a heiroglyph, and the blood of a virgin." -- someeecards

4 5

that ever puzzling special chars escaping + rdiff-backup
by lejeczek 21 Feb '17

21 Feb '17

hi everyone a good basher around here? I try in a script: _rdiffBack="rdiff-backup -v5 --tempdir /tmp/ --no-eas --exclude-other-filesystems --exclude-symbolic-links" _rdffiExclude="--exclude '**/~*' --exclude '**.tmp' --exclude-regexp '(.glusterfs|.trashcan|temp)'" _execCom=${!2} _sourceDir=${1} _backupTo=${3} __backMeUp() { for _sourceDir in ${_sourceDirs[@]}; do echo \$ ${_execCom} ${_rdffiExclude} ${_sourceDir}/ ${_backupTo} \> ${_logFile} | ${_copyToLog} ${_execCom} ${_rdffiExclude} ${_sourceDir}/ ${_backupTo} > ${_logFile} 2>&1 done } case ${1} in rdiffThis) declare -a _sourceDirs=( /0-ALL.DATA/rdiffThis ); __backMeUp ${@} ;; esac this is a snippet which may look obscure but obvious is: rdiff-backup some data, just that. And when I run it as a script ~]$ runme.sh rdiffThis _rdiffBack toHere I see: Fatal Error: Fatal Error: The file specification ''**' cannot match any files in the base directory You notice that the script echos what it is meant to execute, which suffice I copy&paste that echo in bash prompt... and it works!? No "Fatal Error" And the problem seems to specifically be a shell pattern for --exclude. Take two --exclude out, having: _rdffiExclude="--exclude-regexp '(.glusterfs|.trashcan|temp)'" and script works when invoked, fine! I've been fiddling around but failed to make rdiff-backup 1.2.8 play along. Must be something trivial, right? b.w. L

1 1

Latest CentOS-7 image on cloud.centos.org has incorrect checksum
by Jared Baker 21 Feb '17

21 Feb '17

Good day, I initially posted this issue on CentOS-mirror a week ago but did not receive any response. I'm looking for a resolution to a small issue with the cloud image repository for the latest CentOS-7 image. As far as I understand, the latest release of the CentOS-7 image should always be posted to http://cloud.centos.org/centos/7/images/CentOS-7-x86_ 64-GenericCloud.qcow2 The checksum of this file should match the highest numbered version of the cloud image listed in http://cloud.centos.org/centos/7/images/sha256sum.txt However, the actual checksum for CentOS-7-x86_64-GenericCloud.qcow2 is returning as b56ed1a3a489733d3ff91aca2011f8720c0540b9aa27e46dd0b4f575318dd1fa which matches for CentOS-7-x86_64-GenericCloud-1608.qcow2 but NOT CentOS-7-x86_64-GenericCloud-1612.qcow2. The latest image available should be CentOS-7-x86_64-GenericCloud-1612.qcow2 with a checksum of 559bebb4abb2fdf3bd88c917cc11ef b1975bfe4494e666d133a3148ec4e6225d. To further the confusion, the 'Last modified' image is CentOS-7-x86_64-GenericCloud-1611.qcow2 and not -1612. I picked up on this discrepancy because I have a script that monitors & updates our openstack images when new images become available for various distributions. If someone could please correct these inconsistencies it would be greatly appreciated. Thanks, Jared Baker

3 2

centos-openshift-origin
by Vedran.Bartonicek＠tieto.com 21 Feb '17

21 Feb '17

?Hi, Would someone know when to expect to have package origin-master.1.4.0 in repo centos-openshift-origin? Right now the package is available in centos-openshift-origin-testing. -Vedran

2 2

Network conections problems
by Rommel Rodriguez Toirac 20 Feb '17

20 Feb '17

Hi; I have a CentOS 6.8 x86_64 server where just run Oracle 11g 64 bit data base server. Is happen that sometimes it loose all connections (no ping, I can not access via ssh, no TNSping of Oracle server have success). When this happend I make ping from this server to some IP address of my network and then everything work fine again. I check logs looking for some mistake or problem in the network device, but I do not find anything or maybe I not looking where must be. I check that from a workstation (Windows XP or Windows 7 or Windows 10) when I make ping to the server, after ~ 8 seconds in get answer and always the first one is loose. If you try again ping, everything work fine (no answers are loose) C:\Users\administrator>ping pgtm.gtm.gob.cu Haciendo ping a pgtm.gtm.gob.cu [192.168.41.4] con 32 bytes de datos: Tiempo de espera agotado para esta solicitud. Respuesta desde 192.168.41.4: bytes=32 tiempo<1m TTL=64 Respuesta desde 192.168.41.4: bytes=32 tiempo<1m TTL=64 Respuesta desde 192.168.41.4: bytes=32 tiempo<1m TTL=64 Estadísticas de ping para 192.168.41.4: Paquetes: enviados = 4, recibidos = 3, perdidos = 1 (25% perdidos), Tiempos aproximados de ida y vuelta en milisegundos: Mínimo = 0ms, Máximo = 0ms, Media = 0ms This are some of the configs related with networks [root@pgtm ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE=eth0 TYPE=Ethernet UUID=11dcddd4-6530-457a-8d3e-01a8339fb113 ONBOOT=yes NM_CONTROLLED=yes BOOTPROTO=none HWADDR=6C:92:BF:26:C7:02 IPADDR=192.168.41.4 PREFIX=24 GATEWAY=192.168.41.1 DNS1=192.168.41.17 DOMAIN=gtm.gob.cu DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME="System eth0" cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.41.4 pgtm pgtm.gtm.gob.cu [root@pgtm ~]# cat /etc/resolv.conf # Generated by NetworkManager search gtm.gob.cu nameserver 192.168.41.17 [root@pgtm mail]# cat /etc/sysconfig/network NETWORKING=yes HOSTNAME=pgtm.gtm.gob.cu GATEWAY=192.168.41.1 Someone that happend something like this, or some place for where keep looking to try to fix this loose of conection? Thank and sorry for my horryble English. Rommel Rodriguez Toirac rommelrt(a)nauta.cu

2 1

Re: [CentOS] usb drives & Orico ORICO 9548U3-BK
by tdukes＠palmettoshopper.com 20 Feb '17

20 Feb '17

> -----Original Message----- > From: CentOS [mailto:centos-bounces@centos.org] OnBehalf Of Gregory P. > Ennis > Sent: Sunday, February 19, 2017 12:31 PM > To: centos(a)centos.org > Subject: Re: [CentOS] usb drives & Orico ORICO9548U3-BK > > > > > > I decided to build an archive server for thepurpose of backing up > > other fedora/centos desktops at theoffice. I built a machine and > > have installed Centos 7.3 on it with all updatescurrent. I also > > purchased a 3.0 usb sata drive cabinet (OricoORICO 9548U3-BK) and > > installed two 5T black WDdrives. There was no problem installing > > the usb cabinet or the drives. Iformatted each drive with xfs as > > /dev/sdc and /dev/sdd, and then combined theminto a software mirrored > > raid with mdadm as /dev/md0. > > I've always thought that the perceived wisdom is tonot try and do software > raid across USB - especially when both drives are atthe other end of the > same USB cable. Sure USB 3 is faster and there's abetter chance it will appear > to work at a reasonable speed, but it's notsomething I would contemplate. > > > > > Everything was working perfectly until Iremoved the terminal, > > keyboard and mouse and tried to reboot themachine. It took a while > > to figure out, but when the mouse and keyboardwere removed the boot > > process assigns the usb drives differentlywhich makes /dev/md0 > > created by mdadm fail. > > Which means that the drive letters are explicitlymentioned in > /etc/mdadm.conf - you can change it to be wildcardedor leave mdadm to > figure it all out itself. See 'manmdadm.conf'. > > > > > My fstab file looks like : > > > > /dev/mapper/centos_poar-root / xfs defaults 0 > > 0 > > UUID=f915a354-28bf-4110-bec9-3767ef1fe52c/boot xfs defaults 0 > > 0 > >/dev/mapper/centos_poar-home /home xfs defaults 0 > > 0 > >/dev/mapper/centos_poar-u /u xfs defaults 0 > > 0 > >/dev/mapper/centos_poar-swap swap swap defaults 0 > > 0 > >/dev/sda /u0 btrfs defaults 0 > > 0 > > # entries below were combined into one mirroredraid system > #/dev/sdc > >/u1 xfs defaults 0 > > 0 > >#/dev/sdd /u2 xfs defaults 0 > > 0 > >/dev/md0 /u1 xfs defaults 0 > > 0 > > Another likely issue is that you explicitly mention/dev/sda in the fstab - if the > drives are re-ordered, then /dev/sda will not bewhat you think it is. It's a > much better idea to use UUIDs when mounting drives.You can find the UUID > with > > lsblk --fs /dev/sda > > BTW, are you really using partitionless disks - isit really /dev/sda and not > /dev/sda1 ? > > > > > > > This works perfectly when a usb mouse and a usbkeyboard are attached, > > but when I remove the mouse and keyboard thesystem will not boot > > because the usb drives are relabeled as/dev/sda and /dev/sdb. > > I would have thought that any SATA drives would havebeen processed > before the USB drives - certainly it looks that wayon my system. Try going > through the output of dmesg to see if you can seewhat is really happening > when in the boot sequence. > > > > > > > My thought is that if I could force the usbdrives to be labeled as > > /dev/sdc and /dev/sdd whether the mouse andkeyboard are attached or > > not, I might be able to fix the problem > > It's much easier to make sure you don't explicitlyuse drive letters - because, > as you've found out, they can change. Usefilesystem labels or UUIDs or disk > IDs. The disk IDs can be found in /dev/disk/by-idand they should remain the > same. > > P. > >----------------------------------------------------------------- > > Pete, > > Thank you for such excellent help; I appreciate yourwisdom and challenges. > The machine I am working on is still at the 'lab'stage so everything can be > changed at this point. I don't have the benefit of much 'perceivedwisdom' in > that most of my knowledge comes from mistakes I havemade or mistakes > others on this list have made that Ican learnfrom. So thanks again. > > Here are some of my thoughts... right or wrong. > > #1. 3.0 USB drives > I originally performed some testing on a small usbpassport 3T drive and was > amazed by the response and access times. I stumbled across the Orico > cabinet during a NewEgg search, and decided to giveit a try. I was even > more impressed with the response and accesstimes. I decided to attempt a > mdadm raid on the the Orico and everything hasworked better than > expected except for the problems I have had withdevice > assignments. I did have an electrical failure at my home related to > weather of which the ups powered down after 30minutes that caused one > of the raid 5T drives to become corrupted. I reformatted the drive and > rebuilt the raid with mdadm, and everything worked alot better than I > expected. Iwill only be using this system to store *.tar.gz backup files from > other systems. What should cause me to fear the USB 3.0 connection. > > #2. /etc/mdadm.conf > The tutorials I read about how to use mdadm did notinclude mdadm.conf, > and this was not created when I installedmdadm. I will take a look at the > man pages.... thank you. > > #3. UUID's > Thanks for the suggestion to use names instead ofdevice addresses and > how to get the names with lsblk --fs /dev/sda. Using this should fix > my problem of reassignment device names at boottime. Thanks much!!! > > #4. Partitionless disks > I orginally installed Centos 7.3 on an SSD, and theninstalled the hard drives > subsequently. I noticed that I gained quite a bit of disc space by not using a > partition. Since the files I will be storing on these discs are large and will only > be accessed for archive purposes I wanted > to use as much of the disk as possible. The original google searches > I made related to using a partitionless disk did notgive me compelling rational > to use a partition, however I would surely like tohear from you and others > about this. > > > Thanks again for your help, and instruction!!!!! > I kinda did the same thing as you. I bought a 4TB WDElements. Disabled the sleep timer. I use UrBackup to backup two local machines, one remote,to my CentOS server. The WD Elements is backing up the CentOS server as wespeak (since 9:00AM this morning). I use a rsync script I found,https://github.com/laurent22/rsync-time-backup I started with REAR, but it created a 1TB tar.gz file soI went with the rsync script. Had to remove the --one-file-system arg.

1 0

mdadm vs raidcheck
by Fred Smith 20 Feb '17

20 Feb '17

Hi all! I don't religiously follow everything that pops up in the selinux alerts, but now and then I go back and look at some of them. (I'm on an up to date Centos-7). Today I noted an error that seems to occur during a weekly raid check, from /etc/cron.d. the selinux alert is: SELinux is preventing /usr/sbin/mdadm from write access on the file /var/log/rear/rear-fcshome.log.lockless. so I go look at that file and find that it contains, down in the middle of commands run, a series of errors: 2017-02-19 01:30:03 Relax-and-Recover 1.17.2 / Git 2017-02-19 01:30:03 Command line options: /usr/sbin/rear checklayout 2017-02-19 01:30:03 Including /etc/rear/os.conf 2017-02-19 01:30:03 Including conf/Linux-i386.conf 2017-02-19 01:30:03 Including conf/GNU/Linux.conf 2017-02-19 01:30:04 Including /etc/rear/local.conf 2017-02-19 01:30:04 Running 'init' stage 2017-02-19 01:30:04 Including init/default/01_set_drlm_env.sh 2017-02-19 01:30:04 Finished running 'init' stage in 0 seconds 2017-02-19 01:30:04 Using build area '/tmp/rear.oaWHSvnwNFddStm' 2017-02-19 01:30:04 Running checklayout workflow 2017-02-19 01:30:04 Running 'layout/precompare' stage 2017-02-19 01:30:04 Including layout/precompare/default/11_check_layout_file.sh 2017-02-19 01:30:04 Finished running 'layout/precompare' stage in 0 seconds 2017-02-19 01:30:04 Running 'layout/save' stage 2017-02-19 01:30:04 Including layout/save/GNU/Linux/10_create_layout_file.sh 2017-02-19 01:30:04 Creating disk layout 2017-02-19 01:30:04 Preparing layout directory. 2017-02-19 01:30:04 Including layout/save/GNU/Linux/15_save_diskbyid_mappings.sh 2017-02-19 01:30:05 Saved diskbyid_mappings 2017-02-19 01:30:05 Including layout/save/GNU/Linux/20_partition_layout.sh 2017-02-19 01:30:06 Saving disk partitions. 2017-02-19 01:30:08 Including layout/save/GNU/Linux/21_raid_layout.sh 2017-02-19 01:30:08 Saving Software RAID configuration. /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 44: let: sparedevices=-: syntax error: operand expected (error token is "-") /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 65: [: : integer expression expected /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 44: let: sparedevices=-: syntax error: operand expected (error token is "-") /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 65: [: : integer expression expected /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 44: let: sparedevices=-: syntax error: operand expected (error token is "-") /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 65: [: : integer expression expected /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 44: let: sparedevices=-: syntax error: operand expected (error token is "-") /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh: line 65: [: : integer expression expected 2017-02-19 01:30:09 Including layout/save/GNU/Linux/22_lvm_layout.sh 2017-02-19 01:30:09 Saving LVM layout. 2017-02-19 01:30:11 Including layout/save/GNU/Linux/23_filesystem_layout.sh 2017-02-19 01:30:11 Begin saving filesystem layout 2017-02-19 01:30:11 Saving filesystem layout (using the findmnt command). 2017-02-19 01:30:16 End saving filesystem layout 2017-02-19 01:30:16 Including layout/save/GNU/Linux/24_swaps_layout.sh 2017-02-19 01:30:16 Saving Swap information. 2017-02-19 01:30:16 Including layout/save/GNU/Linux/25_drbd_layout.sh 2017-02-19 01:30:16 Including layout/save/GNU/Linux/26_crypt_layout.sh 2017-02-19 01:30:16 Saving Encrypted volumes. 2017-02-19 01:30:16 Device Mapper name No not found in /dev/mapper. 2017-02-19 01:30:16 Including layout/save/GNU/Linux/27_hpraid_layout.sh 2017-02-19 01:30:16 Including layout/save/GNU/Linux/28_multipath_layout.sh 2017-02-19 01:30:16 Did not find multipath device No in the expected location. 2017-02-19 01:30:16 Including layout/save/default/30_list_dependencies.sh 2017-02-19 01:30:16 Including layout/save/default/31_autoexclude_usb.sh 2017-02-19 01:30:16 Including layout/save/default/31_include_exclude.sh 2017-02-19 01:30:16 Including layout/save/default/32_autoexclude.sh 2017-02-19 01:30:17 Disk /dev/sdb is not used by any mounted filesystem. Excluding. 2017-02-19 01:30:17 Disk /dev/sdc is not used by any mounted filesystem. Excluding. 2017-02-19 01:30:17 Including layout/save/default/33_remove_exclusions.sh 2017-02-19 01:30:17 Including layout/save/GNU/Linux/34_false_blacklisted.sh 2017-02-19 01:30:18 Including layout/save/default/34_generate_mountpoint_device.sh 2017-02-19 01:30:18 Including layout/save/GNU/Linux/35_copy_drbdtab.sh 2017-02-19 01:30:18 Including layout/save/default/40_check_backup_special_files.sh 2017-02-19 01:30:18 Including layout/save/default/45_check_bootloader_files.sh 2017-02-19 01:30:18 Including layout/save/default/45_check_network_files.sh 2017-02-19 01:30:18 Including layout/save/GNU/Linux/50_extract_vgcfg.sh 2017-02-19 01:30:18 Including layout/save/GNU/Linux/51_current_disk_usage.sh 2017-02-19 01:30:19 Including layout/save/default/60_snapshot_files.sh 2017-02-19 01:30:19 Finished running 'layout/save' stage in 15 seconds 2017-02-19 01:30:19 Running 'layout/compare' stage 2017-02-19 01:30:19 Including layout/compare/default/50_compare_layout.sh 2017-02-19 01:30:19 Disk layout is identical. 2017-02-19 01:30:19 Including layout/compare/default/51_compare_files.sh 2017-02-19 01:30:20 Finished running 'layout/compare' stage in 1 seconds 2017-02-19 01:30:20 Finished running checklayout workflow 2017-02-19 01:30:20 Running exit tasks. 2017-02-19 01:30:20 Finished in 18 seconds 2017-02-19 01:30:20 Removing build area /tmp/rear.oaWHSvnwNFddStm 2017-02-19 01:30:20 End of program reached selinux says it prevent writes to this file. but the file was clearly written to! Is selinux stupid enough to mistake shell errors as a failure to write? Also, in trying to figure out what those errors mean, I looked at the file specified in the errors, /usr/share/rear/layout/save/GNU/Linux/21_raid_layout.sh, where I find line 44 and a couple above it read: ndevices=$( grep "Raid Devices" $TMP_DIR/mdraid | tr -d " " | cut -d ":" -f "2") totaldevices=$( grep "Total Devices" $TMP_DIR/mdraid | tr -d " " | cut -d ":" -f "2") let sparedevices=$totaldevices-$ndevices it appears that "ndevices" and "totaldevices" are both empty (not zero, but empty) because the error report above says "-" isn't valid, which would happen if those two variables were unpopulated. At this point I haven't yet found out where those values come from... (more to the point, I haven't yet figured out where TMP_DIR comes from) If any of you know more than I (I've never seen this code before) I'd appreciate a pointer, but I'll keep looking too. In the meantime, my software raid seems to keep chugging along. thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ---------------------------- Do you not know? Have you not heard? The LORD is the everlasting God, the Creator of the ends of the earth. He will not grow tired or weary, and his understanding no one can fathom. ----------------------------- Isaiah 40:28 (niv) -----------------------------

1 0

usb drives & Orico ORICO 9548U3-BK
by Gregory P. Ennis 19 Feb '17

19 Feb '17

Everyone, Is there a way to manually assign usb drives to a specified device label. Is there a way to force two usb drives to be labeled as /dev/sdc and /dev/sdd? I decided to build an archive server for the purpose of backing up other fedora/centos desktops at the office. I built a machine and have installed Centos 7.3 on it with all updates current. I also purchased a 3.0 usb sata drive cabinet (Orico ORICO 9548U3-BK) and installed two 5T black WD drives. There was no problem installing the usb cabinet or the drives. I formatted each drive with xfs as /dev/sdc and /dev/sdd, and then combined them into a software mirrored raid with mdadm as /dev/md0. Everything was working perfectly until I removed the terminal, keyboard and mouse and tried to reboot the machine. It took a while to figure out, but when the mouse and keyboard were removed the boot process assigns the usb drives differently which makes /dev/md0 created by mdadm fail. My fstab file looks like : /dev/mapper/centos_poar-root / xfs defaults 0 0 UUID=f915a354-28bf-4110-bec9-3767ef1fe52c /boot xfs defaults 0 0 /dev/mapper/centos_poar-home /home xfs defaults 0 0 /dev/mapper/centos_poar-u /u xfs defaults 0 0 /dev/mapper/centos_poar-swap swap swap defaults 0 0 /dev/sda /u0 btrfs defaults 0 0 # entries below were combined into one mirrored raid system #/dev/sdc /u1 xfs defaults 0 0 #/dev/sdd /u2 xfs defaults 0 0 /dev/md0 /u1 xfs defaults 0 0 This works perfectly when a usb mouse and a usb keyboard are attached, but when I remove the mouse and keyboard the system will not boot because the usb drives are relabeled as /dev/sda and /dev/sdb. The only way I have been able to make this archive server function is to keep a mouse and keyboard plugged in to the system, and even with the keyboard and mouse attached I can not do a software reboot, I am required to turn off the power supply for a couple of seconds and then turn it back on before I hit the power switch on the computer. I have played with the bios setting until my eyes are blurry, but have not been able to solve the problem. I am using a ASUS H110M-E/M.2 LGA 1151 Intel H110 HDMI SATA 6Gb/s USB 3.0 Micro ATX Motherboard. My thought is that if I could force the usb drives to be labeled as /dev/sdc and /dev/sdd whether the mouse and keyboard are attached or not, I might be able to fix the problem Anyone have any ideas? Thanks for your responses!!!! Greg Ennis

3 3

RAID questions
by tdukes＠palmettoshopper.com 19 Feb '17

19 Feb '17

Hello, Just a couple questions regarding RAID. Here's thesituation. I bought a 4TB drive before I upgraded from 6.8 to 7.3. I'm not too far into this that Ican't start over. I wanted disk space to backup 3 other machines. I way overestimated what I needed for full, incremental and image backups with UrBackup.I've used less than 1TB so far. I would like to add an additional drive to makeit a RAID server. I may use a PCIe SSD for the boot drive if I can find onecompatible with my old hardware. 1- Better to go with a hardware RAID (mainboardsupported) or software? 2 - Can an existing drive with data on it be used as aRAID drive without losing current data? 3 - Can additional drive(s) be added later with a changein RAID level without current data loss? TIA

8 11

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss