Re: [CentOS] Journal Aborts in VMware ESX (Filesystem Corruption)
On Sun, Feb 13, 2011 at 4:03 PM, Adam Tauno Williams awill...@whitemice.org wrote: On Sun, 2011-02-13 at 20:28 +, Keith Beeby wrote: Also seeing this issue with CentOS 5.4 and 5.5 with NFS shared storage, according the the VMware knowledge base article this should have been resolved in v5.1 update??. Does changing the vm.min_free_kbytes valu apply CentOS v.5.4 and 5.5 as well to resolve the issue? I guess we'll see [this issue has become extremely frustrating]. I suppose it is 'good' to see that someone else sees the issue as well. One issue with virtualization is that debugging these types of issues is an order-of-magnitude more difficult [virtualized OS, virtualized storage, virtualization platform, or some interaction of all the above... ugh]. I am experiencing the same issue. cent: current exsi v3.5 update 5 storage nfs I am in the process of rebuilding the virtual server using a different os thinking it was just file system errors. -bazooka ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] how to automount usb drive
I have a server with no desktop - just cli that i need to have a user plug in a usb hd and would like it to automount to a consistent directory so I can schedule a backup. The user can rotate the usb drives and it all just works. Any ideas how automate so that say /media/backup mounts to any usb harddrive and unmounts cleanly? -thx bazooka ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] rescan usb hd
I have a usb hd that I use for backup. Occasionally it dies. scsi 6:0:0:0: rejecting I/O to dead device scsi 6:0:0:0: rejecting I/O to dead device scsi 6:0:0:0: rejecting I/O to dead device scsi 6:0:0:0: rejecting I/O to dead device Buffer I/O error on device sdc1, logical block 0 lost page write due to I/O error on sdc1 EXT2-fs error (device sdc1): read_inode_bitmap: Cannot read inode bitmap - block_group = 129, inode_bitmap = 4227073 scsi 6:0:0:0: rejecting I/O to dead device scsi 6:0:0:0: rejecting I/O to dead device scsi 6:0:0:0: rejecting I/O to dead device Buffer I/O error on device sdc1, logical block 0 lost page write due to I/O error on sdc1 EXT2-fs error (device sdc1): ext2_readdir: bad page in #2 scsi 6:0:0:0: rejecting I/O to dead device scsi 6:0:0:0: rejecting I/O to dead device Buffer I/O error on device sdc1, logical block 0 lost page write due to I/O error on sdc1 EXT2-fs error (device sdc1): ext2_get_inode: unable to read inode block - inode=2, block=1027 scsi 6:0:0:0: rejecting I/O to dead device scsi 6:0:0:0: rejecting I/O to dead device Buffer I/O error on device sdc1, logical block 0 lost page write due to I/O error on sdc1 EXT2-fs error (device sdc1): ext2_readdir: bad page in #2 If i unmount it and try to remount it it says sdc1 does not exist. I am not at the location so physically unplugging then replugging in the drive isn't a convenient option. How can I get the os to rescan the usb device so I can remount? thx bazooka ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] server is always getting hacked
On Sat, Jun 27, 2009 at 12:21 PM, Mag Gammagaw...@gmail.com wrote: WE have a centos 5.3 install, and our server is keep getting hacked. We see load averages of 500+ and see people from all over the world logging into our server (used last). Is there a good place to start to avoid these kinds of things? For example, here is what I already did. Open up sshd port only setup iptables to only accept port 80 and 22 No FTP No other ports are allowed according to IP Tables. I am not sure what else measures I can take. Can someone please assist? It doesn't matter what you do to harden after you have already been owned. It has been said here but i'll say it again - reinstall. Start fresh then harden then put back on net. You don't give much info on what this server does but as long as you change all passwds and assure they are strong then the only other point of entry would be an insecure web app. I would run a http firewall ie modsecurity. http://www.modsecurity.org/ I was getting hacked because of users apps until i installed modsecurity. I also limit ssh to only users that need it. I also run rkhunter every 30 min in silent mode. Sounds extreme but minimizing the damage a hacker can do means the difference between scheduled down time vs unscheduled. --bazooka ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Email/GroupWare Suite
On Wed, Jan 7, 2009 at 6:36 PM, Max Hetrick maxhetr...@verizon.net wrote: René Standfest wrote: We have running at the moment eGroupWare, but we plan to migrate to SOGo (http://sogo.opengroupware.org) in the next two months (we had some annoying problems with eGW in the past). It has a really cool Webfrontend (looks like Thunderbird with Lightning) and has a really functional CalDAV-Interface which integrates perfectly into Thunderbird/Lightning. On the Website is a really good Install-Howto and it has even a yum repo. Thank you for mentioning sogo. I took a look at this project today, and will be adding it to the list of packages I'm testing. When researching groupware packages before, this project didn't turn up, but am glad you brought it up here. It looks promising and worth a look! I opted for Kolab http://www.kolab.org/ over Zimbra. You can have unlimited users in Kolab. My users wanted to use outlook as the client - Zimbra charges quite a bit for that feature. With Kolab you buy a $10 outlook connector for each computer. Most other mail clients are free to use with Kolab. No package for cent but that is a good thing. It compiles everything it needs using openpkg. I have installed it on cent several times while testing. Just about to take my first installation live. -bazooka ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] saslauthd crashes
I just took my first cent server into production and now saslauthd keep crashing after brute force attack. I found a bug report so this has already been reported but not fixed. http://bugs.centos.org/print_bug_page.php?bug_id=2860 I assume this has to be a large problem for many people and am surprised it hasn't been fixed yet. Has anyone found a work around for this bug? Is there a better rpm repo for a saslauthd that won't crash? -bazooka ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
