Re: [CentOS] Need help getting two NICs to work on CentOS 7

[Boris Epstein]

Hello there,

What is the hypervisor that hosts the VM? What does ifconfig show on it?

Boris.

On Mon, Nov 7, 2016 at 4:36 PM, Gordon Messmer 
wrote:

> On 11/06/2016 11:00 PM, Sean Son wrote:
>
>> How do I
>> configure the networking so that both IPs are pingable and the VM is
>> reachable via both IPs?
>>
>
>
> You need one rule file per interface, which directs traffic out the
> appropriate interface based on the source address of the packet:
>
> https://blogs.oracle.com/networking/entry/advance_routing_for_multi_homed
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] NFS help

[Boris Epstein]

I am sorry, I am stepping into the conversation late and may not fully
understand all aspects of the situation but I wonder if it may make sense
to set up a server process on the NFS server machine that simply listens
for incoming requests to perform a file copy and then does so as requested
- only locally. If files in question are large - which I suspect they may
be, given the timeouts becoming an issue - that may resolve the issue and
help speed things up at the same time.

Cheers,

Boris.


On Wed, Oct 26, 2016 at 9:35 AM, Matt Garman 
wrote:

> On Tue, Oct 25, 2016 at 7:22 PM, Larry Martell 
> wrote:
> > Again, no machine on the internal network that my 2 CentOS hosts are
> > on are connected to the internet. I have no way to download anything.,
> > There is an onerous and protracted process to get files into the
> > internal network and I will see if I can get netperf in.
>
> Right, but do you have physical access to those machines?  Do you have
> physical access to the machine which on which you use PuTTY to connect
> to those machines?  If yes to either question, then you can use
> another system (that does have Internet access) to download the files
> you want, put them on a USB drive (or burn to a CD, etc), and bring
> the USB/CD to the C6/C7/PuTTY machines.
>
> There's almost always a technical way to get files on to (or out of) a
> system.  :)  Now, your company might have *policies* that forbid
> skirting around the technical measures that are in place.
>
> Here's another way you might be able to test network connectivity
> between C6 and C7 without installing new tools: see if both machines
> have "nc" (netcat) installed.  I've seen this tool referred to as "the
> swiss army knife of network testing tools", and that is indeed an apt
> description.  So if you have that installed, you can hit up the web
> for various examples of its use.  It's designed to be easily scripted,
> so you can write your own tests, and in theory implement something
> similar to netperf.
>
> OK, I just thought of another "poor man's" way to at least do some
> sanity testing between C6 and C7: scp.  First generate a huge file.
> General rule of thumb is at least 2x the amount of RAM in the C7 host.
> You could create a tarball of /usr, for example (e.g. "tar czvf
> /tmp/bigfile.tar.gz /usr" assuming your /tmp partition is big enough
> to hold this).  Then, first do this: "time scp /tmp/bigfile.tar.gz
> localhost:/tmp/bigfile_copy.tar.gz".  This will literally make a copy
> of that big file, but will route through most of of the network stack.
> Make a note of how long it took.  And also be sure your /tmp partition
> is big enough for two copies of that big file.
>
> Now, repeat that, but instead of copying to localhost, copy to the C6
> box.  Something like: "time scp /tmp/bigfile.tar.gz  host>:/tmp/".  Does the time reported differ greatly from when you
> copied to localhost?  I would expect them to be reasonably close.
> (And this is another reason why you want a fairly large file, so the
> transfer time is dominated by actual file transfer, rather than the
> overhead.)
>
> Lastly, do the reverse test: log in to the C6 box, and copy the file
> back to C7, e.g. "time scp /tmp/bigfile.tar.gz  host>:/tmp/bigfile_copy2.tar.gz".  Again, the time should be
> approximately the same for all three transfers.  If either or both of
> the latter two copies take dramatically longer than the first, then
> there's a good chance something is askew with the network config
> between C6 and C7.
>
> Oh... all this time I've been jumping to fancy tests.  Have you tried
> the simplest form of testing, that is, doing by hand what your scripts
> do automatically?  In other words, simply try copying files between C6
> and C7 using the existing NFS config?  Can you manually trigger the
> errors/timeouts you initially posted?  Is it when copying lots of
> small files?  Or when you copy a single huge file?  Any kind of file
> copying "profile" you can determine that consistently triggers the
> error?  That could be another clue.
>
> Good luck!
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] IPMI ??

[Boris Epstein]

Keith,

I am sorry, unfortunately I don't remember model numbers. Those were Dell
boxes as far as I remember.

Boris.

On Sun, Sep 18, 2016 at 7:03 PM, Keith Keller <
kkel...@wombat.san-francisco.ca.us> wrote:

> On 2016-09-18, Boris Epstein <borepst...@gmail.com> wrote:
> > Is there a little setup display right on the box? Just asking because I
> > have seen that on some boxes.
>
> You mean for configuring the IPMI interface?  I've never seen that but
> it sounds very cool.  Do you have specific references for systems which
> you've seen that on?
>
> --keith
>
> --
> kkel...@wombat.san-francisco.ca.us
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] IPMI ??

[Boris Epstein]

Is there a little setup display right on the box? Just asking because I
have seen that on some boxes.

Cheers,

Boris.

On Sun, Sep 18, 2016 at 12:15 AM, Keith Keller <
kkel...@wombat.san-francisco.ca.us> wrote:

> On 2016-09-17, Alice Wonder  wrote:
> >
> > Okay if it requires DHCP this might be out, I'm currently out of town
> > watching my brothers (various disabilities) while parents are on much
> > needed vacation. Don't have easy physical access to the router, would
> > have to take out stuff in front of it. Was hoping crossover ethernet
> > would work.
>
> It probably would, but you still need some way to assign an IP address
> to the IPMI interface (it probably doesn't have one out of the box).
> But from your laptop you can run a DHCP server which would then assign
> an IP to the IPMI interface.
>
> The IPMI might self-assign if it can't find a DHCP server, but in my
> memory (which might be faulty) it doesn't do this.
>
> If for some reason Java doesn't work from your browser, Supermicro also
> distributes a Java GUI tool for interacting with Supermicro IPMI
> interfaces.  It also supports a subnet scanner, so you don't need to
> know the IP that gets assigned.  Look for IPMIview here:
>
> http://www.supermicro.com/products/nfo/IPMI.cfm
>
> It's not a great tool but it works well enough for console access.
>
> --keith
>
> --
> kkel...@wombat.san-francisco.ca.us
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] php55w-fpm on CentOS 7: settings location

[Boris Epstein]

OK, here's the PHP info:

http://borisepstein.info/php.php

Looks like it got the right php.ini but that is still not happening. Is
there any chance something overwrote the variable settings after php.ini
was read in?

Boris.


On Wed, Aug 3, 2016 at 2:27 PM, Valeri Galtsev 
wrote:

>
> On Wed, August 3, 2016 1:19 pm, Always Learning wrote:
> >
> > On Wed, 2016-08-03 at 13:55 -0400, Jason Welsh wrote:
> >
> >> What I do is create a  php.php file on the root of my fileserver with
> >> the following
> >>
> >> 
> >
> > I use a text command: php -i
> >
>
> I like more the way Jason pointed to: this is one step closer to what is
> actually used by web server as opposed to command line.
>
> Just my $0.02
>
> Valeri
>
> 
> Valeri Galtsev
> Sr System Administrator
> Department of Astronomy and Astrophysics
> Kavli Institute for Cosmological Physics
> University of Chicago
> Phone: 773-702-4247
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] php55w-fpm on CentOS 7: settings location

[Boris Epstein]

Hello all,

Does anybody know where to enter settings for php-fpm? I have tried a
number of things, including starting it with "-c /etc/php.ini" but that
seemed to have any effect. Any idea on how to control it? What am I doing
wrong? :)

Thanks in advance.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Install C7 VM on C6 Host

[Boris Epstein]

I would think the same as Gordon that as long as your 64-bit VM
virtualization is running properly there should be no problem running C7 on
a VM running under C6. May I ask what the initial doubt was based upon? Has
anybody out there had such an issue before?

Cheers,

Boris.


On Tue, Jun 21, 2016 at 7:30 PM, Gordon Messmer 
wrote:

> On 06/21/2016 04:06 PM, Mark LaPierre wrote:
>
>> Before I waste myself a bunch of time trying the impossible I figured I
>> would ask if I can install an instance of C7 in a KVM based VM on a C6
>> host.
>>
>
>
> Yes.
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Perl on CentOS 6 and CentOS 7

[Boris Epstein]

On Mon, Mar 14, 2016 at 12:47 PM, John R Pierce  wrote:

> On 3/14/2016 9:35 AM, Valeri Galtsev wrote:
>
>> But packages aside, as Linux is UNIX-like system, you can always install
>> it UNIX way: download tarball from perl site, compile and install it. You
>> will have to do your own work maintaining it whenever updates are
>> necessary.
>>
>
> just don't replace the stuff in the system directories.   build your
> custom perl to live in /usr/local or /opt or something.
>
> --
> john r pierce, recycling bits in santa cruz
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

Thanks, sure, all of the above makes sense. My question was primarily aimed
at those who have at least tried to run Perl 6 on CentOS and actually have
some practical experience to report.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Perl on CentOS 6 and CentOS 7

[Boris Epstein]

Hello listmates,

What are the proven/tested version of Perl for CentOS 6 and 7? Is Perl 6
operational on either?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] OpenSSH security flaw

[Boris Epstein]

Hello all,

Does anybody know if this one has been patched?

http://thehackernews.com/2016/01/openssh-vulnerability-cryptokeys.html

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device

[Boris Epstein]

On Thu, Nov 5, 2015 at 8:23 AM, Tris Hoar <trish...@bgfl.org> wrote:

> On 04/11/2015 20:59, John R Pierce wrote:
>
>> On 11/4/2015 12:52 PM, Boris Epstein wrote:
>>
>>> I don't get this for some reason... not even sure why. ESXi's default
>>> behaviour seems to be to allow hotplug, that does not seem to be
>>> deactivated. I am just not sure. Wonder if this could be the Centos 7
>>> vs 6
>>> - perhaps that is what I ought to test for.
>>>
>>
>> what virtual SCSI controller type are you using for these VM's? Mine are
>> 'paravirtual'.
>>
>>
> Also, what guest OS and VM hardware version is the guest running as?
>
> Tris
>
>
> *
> This email and any files transmitted with it are confidential
> and intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> postmas...@bgfl.org
>
> The views expressed within this email are those of the individual, and not
> necessarily those of the organisation
> *
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

Tris, John,

Thanks!

I blew away the original VM I was using for testing as it came time to do
the things for real in production - and, as much as I hated it, I just
added the disk and rebooted the production machine to make it "see" that
disk.

However, I have then decided to investigate the matter further. So I
created a new one. It is  running on an ESXi 5.5 server, VM Version 10,
VMware Paravirtual SCSI controller, configured for RedHat 6/64-bit OS,
running Centos 6/64 bit. And it worked perfectly when it came to "seeing" a
hotplugged disk drive.

So I am not sure what to make of all of it - but it looks like freshly
created VM's are OK and it was indeed something to do with the VM settings.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device

[Boris Epstein]

On Fri, Nov 6, 2015 at 9:56 AM, Boris Epstein <borepst...@gmail.com> wrote:

>
>
> On Thu, Nov 5, 2015 at 8:23 AM, Tris Hoar <trish...@bgfl.org> wrote:
>
>> On 04/11/2015 20:59, John R Pierce wrote:
>>
>>> On 11/4/2015 12:52 PM, Boris Epstein wrote:
>>>
>>>> I don't get this for some reason... not even sure why. ESXi's default
>>>> behaviour seems to be to allow hotplug, that does not seem to be
>>>> deactivated. I am just not sure. Wonder if this could be the Centos 7
>>>> vs 6
>>>> - perhaps that is what I ought to test for.
>>>>
>>>
>>> what virtual SCSI controller type are you using for these VM's? Mine are
>>> 'paravirtual'.
>>>
>>>
>> Also, what guest OS and VM hardware version is the guest running as?
>>
>> Tris
>>
>>
>> *
>> This email and any files transmitted with it are confidential
>> and intended solely for the use of the individual or entity to whom they
>> are addressed. If you have received this email in error please notify
>> postmas...@bgfl.org
>>
>> The views expressed within this email are those of the individual, and
>> not necessarily those of the organisation
>> *
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
>
> Tris, John,
>
> Thanks!
>
> I blew away the original VM I was using for testing as it came time to do
> the things for real in production - and, as much as I hated it, I just
> added the disk and rebooted the production machine to make it "see" that
> disk.
>
> However, I have then decided to investigate the matter further. So I
> created a new one. It is  running on an ESXi 5.5 server, VM Version 10,
> VMware Paravirtual SCSI controller, configured for RedHat 6/64-bit OS,
> running Centos 6/64 bit. And it worked perfectly when it came to "seeing" a
> hotplugged disk drive.
>
> So I am not sure what to make of all of it - but it looks like freshly
> created VM's are OK and it was indeed something to do with the VM settings.
>
> Cheers,
>
> Boris.
>
>
Hello all,

OK, looks like I have figured it out. It seems to be a matter of the SCSI
bus emulation: things work fine with the Paravirtual but do not with the
LSI Parallel.

Good to know:)

Thanks for all your help, everybody.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device

[Boris Epstein]

>>
> vmware esxi 5.5.0 (free, using vsphere client to manage), vm is minimal
> centos 7 64bit.   I added a 16gb vdisk and immediately see this in dmesg...
>
> [155484.386792] vmw_pvscsi: msg type: 0x0 - MSG RING: 1/0 (5)
> [155484.386796] vmw_pvscsi: msg: device added at scsi0:1:0
> [155484.388250] scsi 0:0:1:0: Direct-Access VMware   Virtual disk
>  1.0  PQ: 0 ANSI: 2
> [155484.391275] sd 0:0:1:0: [sdb] 33554432 512-byte logical blocks: (17.1
> GB/16.0 GiB)
> [155484.391552] sd 0:0:1:0: [sdb] Write Protect is off
> [155484.391556] sd 0:0:1:0: [sdb] Mode Sense: 61 00 00 00
> [155484.391593] sd 0:0:1:0: [sdb] Cache data unavailable
> [155484.391595] sd 0:0:1:0: [sdb] Assuming drive cache: write through
> [155484.396148]  sdb: unknown partition table
> [155484.396356] sd 0:0:1:0: [sdb] Attached SCSI disk
>
> and lsblk shows...
>
> # lsblk
> NAME  MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
> sda 8:00   32G  0 disk
> 
> sdb 8:16   0   16G  0 disk
> ...
>
> so I can immediately...
>
> # mkfs.xfs /dev/sdb
> meta-data=/dev/sdb   isize=256agcount=4, agsize=1048576
> blks
> .
> # mount /dev/sdb /mnt
> #
>
> (normally, I'd partition and lvm it, this is just for demo)
> I'm using a paravirtual scsi controller, and have previously installed
> open-vm-tools via yum.
>
> I then umounted it, and in vsphere deleted the vdisk and dmesg immediately
> shows...
>
> [155820.730477] vmw_pvscsi: msg type: 0x1 - MSG RING: 2/1 (5)
> [155820.730481] vmw_pvscsi: msg: device removed at scsi0:1:0
> [155820.754176] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [155820.754247] sr 2:0:0:0: Attached scsi generic sg1 type 5
>
>
> I also did much the same with a CentOS 6.7 VM, also using a 'paravirtual
> SCSI' vm on the same esxi host, when I added the vdisk, it immediately
> shows...
>
> # dmesg
> .
> vmw_pvscsi: msg type: 0x0 - MSG RING: 1/0 (5)
> vmw_pvscsi: msg: device added at scsi0:1:0
> scsi 2:0:1:0: Direct-Access VMware   Virtual disk 1.0  PQ: 0 ANSI:
> 2
> sd 2:0:1:0: Attached scsi generic sg2 type 0
> sd 2:0:1:0: [sdb] 33554432 512-byte logical blocks: (17.1 GB/16.0 GiB)
> sd 2:0:1:0: [sdb] Write Protect is off
> sd 2:0:1:0: [sdb] Mode Sense: 61 00 00 00
> sd 2:0:1:0: [sdb] Cache data unavailable
> sd 2:0:1:0: [sdb] Assuming drive cache: write through
> sd 2:0:1:0: [sdb] Cache data unavailable
> sd 2:0:1:0: [sdb] Assuming drive cache: write through
>  sdb: unknown partition table
> sd 2:0:1:0: [sdb] Cache data unavailable
> sd 2:0:1:0: [sdb] Assuming drive cache: write through
> sd 2:0:1:0: [sdb] Attached SCSI disk
>
> # lsblk
> NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
> sr0 11:01 1024M  0 rom
> sda  8:00   16G  0 disk
> ├─sda1   8:10  500M  0 part /boot
> └─sda2   8:20 15.5G  0 part
>   ├─vg_svfisc6test5-lv_root (dm-0) 253:00  9.6G  0 lvm  /
>   └─vg_svfisc6test5-lv_swap (dm-1) 253:10  5.9G  0 lvm  [SWAP]
> sdb  8:16   0   16G  0 disk
>
> and I note this VM is *not* running vmware tools
>
> NEITHER of these two VMs required rebooting or any echo "- - -"
> >/sys/scsi/.. stuffs.
>
>
> --
> john r pierce, recycling bits in santa cruz
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>


John,

Thanks for your input.

I don't get this for some reason... not even sure why. ESXi's default
behaviour seems to be to allow hotplug, that does not seem to be
deactivated. I am just not sure. Wonder if this could be the Centos 7 vs 6
- perhaps that is what I ought to test for.

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device

[Boris Epstein]

On Wed, Nov 4, 2015 at 1:57 PM, <m.r...@5-cent.us> wrote:

> Boris Epstein wrote:
> >>
> >> My turn for a dumb question: from not paying a lot of attention to this
> >> thread, the answer isn't clear to me: has the *host* recognized the
> >> disk? If not, the guest's not going to see it.
> >
> > IMO your question is not dumb at all. Unfortunately, I don't have an
> > answer to it.
> >
> > All I know is, you reboot the VM and it all works as expected.
>
> Ok, if rebooting the VM, and *only* the VM, fixes it in the VM, then the
> host - the system the VM's running on - knows about the drive. You see
> where I was going with that
>
>mark
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

Mark,

Absolutely, I see your point. This was the starting point - you add the
device on the ESXi server, you reboot the VM, the VM sees the device, no
problem. Now, I ask - do I have to reboot the VM? Logically I hope there
ought to be a way for me not to have to do that - but I have yet to figure
out how to get there.

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device

[Boris Epstein]

Hello Julius,

Thanks - but it doesn't seem to work.

I installed sg3_utils and ran
#scsi-rescan

but that seemed to have done nothing for some reason.

Cheers,

Boris.


On Wed, Nov 4, 2015 at 10:12 AM, Tnjulius <tnjul...@gmail.com> wrote:

> Hi Boris,
> Just rescan the scsi host.
> #scsi-rescan #if you have sg3_utils package
> #lsscsi
> Or
> #echo "- - -" > /sys/class/scsi_host/host[n]/scan
>
> Julius
>
> > On Nov 4, 2015, at 15:31, Boris Epstein <borepst...@gmail.com> wrote:
> >
> > Hello all,
> >
> > Is there a way to recognize a hot-plugged disk (i.e., to get the system
> to
> > recognize it and build the appropriate /dev/sd* device for the new
> device)
> > without a reboot?
> >
> > Thanks.
> >
> > Boris.
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://lists.centos.org/mailman/listinfo/centos
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device

[Boris Epstein]

Hello all,

Is there a way to recognize a hot-plugged disk (i.e., to get the system to
recognize it and build the appropriate /dev/sd* device for the new device)
without a reboot?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device

[Boris Epstein]

On Wed, Nov 4, 2015 at 11:03 AM, Jonathan Billings 
wrote:

> On Wed, Nov 04, 2015 at 05:39:59PM +0200, Eero Volotinen wrote:
> > I think, this is possible with scsi disks
> >
> >
> http://www.cyberciti.biz/tips/vmware-add-a-new-hard-disk-without-rebooting-guest.html
>
> While I believe that this URL has technically correct advice, it's
> basically doing a subset of the commands in the scsi-rescan script in
> the sg3_utils package.
>
> I wonder if you need to be running the vmware tools for the kernel to
> detect new devices?
>
> --
> Jonathan Billings 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

Jonathan,

Thanks, good point. I do have VMware tools running on the VM, though.

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device

[Boris Epstein]

>
>
>
> was the controller you added the virtual disk to an IDE or scsi controller?
>
> --
> public gpg key id: 1362BA1A
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

It was a SCSI controller.

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device

[Boris Epstein]

On Wed, Nov 4, 2015 at 11:29 AM, Eero Volotinen <eero.voloti...@iki.fi>
wrote:

> It should work fine. What esxi version you are using?
>
> Eero
> 4.11.2015 6.27 ip. "Boris Epstein" <borepst...@gmail.com> kirjoitti:
>
>
Eero,

I know. It is EXSi 5.5

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device

[Boris Epstein]

Zep,

Thanks - nothing insulting about asking questions.

I did run this command as root as I would never run stuff like this as any
other user (or, perhaps, I'd use sudo if so forced).

dmesg did not seem to detect the device addition, no.

Cheers,

Boris.


On Wed, Nov 4, 2015 at 10:32 AM, zep <zgreenfel...@gmail.com> wrote:

>
>
> On 11/04/2015 10:27 AM, Mauricio Tavares wrote:
> > On Wed, Nov 4, 2015 at 10:22 AM, Boris Epstein <borepst...@gmail.com>
> wrote:
> >> Hello Julius,
> >>
> >> Thanks - but it doesn't seem to work.
> >>
> >> I installed sg3_utils and ran
> >> #scsi-rescan
> >>
> >> but that seemed to have done nothing for some reason.
> >>
> >   Dumb question: did dmesg even bother to notice *something* was
> attached?
>
> possibly dumb question, possibly unintentionally insulting your
> intelligence...
> you know that when he said "run # scsi-rescan" that meant 'type in
> "scsi-rescan" as the root user', right?  and not '#scsi-rescan'?
> #anything will always appear to do nothing as the shell thinks you're
> typing in a comment.I only ask because I've never seen anyone
> respond with "I ran #command".
>
>
> >
> >> Cheers,
> >>
> >> Boris.
> >>
> >
>
> --
> public gpg key id: 1362BA1A
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device

[Boris Epstein]

>
>
> It usually works very nice here,
> Have you added only the disk or by accident another scsi controller?
> This happens (you probably know) if you select another bus while creating
> the disc.
>
> VG Rainer
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

Rainer,

Thanks.

It looks like I just created another disk on the same controller as I
intended - and once I rebooted the VM it worked just fine - I got my disks
(/dev/sda through /dev/sdd) accessible and functional.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] getting a CentOS6 VM on VMware ESXi platform to recognize a new disk device

[Boris Epstein]

>
>
> My turn for a dumb question: from not paying a lot of attention to this
> thread, the answer isn't clear to me: has the *host* recognized the disk?
> If not, the guest's not going to see it.
>
>   mark
>
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

Mark,

IMO your question is not dumb at all. Unfortunately, I don't have an answer
to it.

All I know is, you reboot the VM and it all works as expected.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] safest way to grow a LV under VMware ESXi5.5

[Boris Epstein]

>
>
> Ok, that *is* small. I'd worry about a logfile suddenly growing massively,
> and freezing your system. (Yes, it has happened here, and then there was
> the time a summer student ran something, wouldn't be back until Monday...
> and got a 20G logfile, which blew out the NFS-mounted home directory fs,
> on which a number of other people resided... including *me*, and his
> manager, and our division head)
>
>mark
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

Mark,

Absolutely - plus, we just need more space:)

Does it make any difference whether to use full disk device for your LV
(i.e., /dev/sdc or some such) or make a partition instead (say, /dev/sdc1
covering the whole disk end to end)? I mean, are there any pro's and con's
to using either as extra space for the logical group?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] safest way to grow a LV under VMware ESXi5.5

[Boris Epstein]

Hello all,

In your view, what is the most reliable and safe way to increase an LV
housing the root filesystem of a Centos 6 VM. I am thinking either growing
the virtual HD virtual device, or creating a new device and adding it as a
PV to the VM, or perhaps migrating the whole FS to a new virtual disk.

Any input on how best to proceed would be appreciated.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] safest way to grow a LV under VMware ESXi5.5

[Boris Epstein]

On Fri, Oct 30, 2015 at 12:57 PM, <m.r...@5-cent.us> wrote:

> Boris Epstein wrote:
> > Hello all,
> >
> > In your view, what is the most reliable and safe way to increase an LV
> > housing the root filesystem of a Centos 6 VM. I am thinking either
> growing
> > the virtual HD virtual device, or creating a new device and adding it as
> a
> > PV to the VM, or perhaps migrating the whole FS to a new virtual disk.
> >
> > Any input on how best to proceed would be appreciated.
> >
> Dumb question: why do you need a larger root filesystem?
>
> First, how big is root? And if this is for stuff under, say, /var/www, I'd
> make a separate logical drive/partition, and mount that, rsync everything
> from /var/www to that, then shut down the web, and remount the new
> filesystem on /var/www.
>
> Root, itself, doesn't need to be huge. We're using 500G, and seriously
> considering making it 125G in the future, with data, or web stuff, is on a
> separate partition, so when there's a sudden explosion of data, / is safe.
>
>mark
>


Mark,

Thanks for your input.

Well, we are talking much smaller scale here (only about 30 GB at present,
planning to roughly double it).

I agree with you that it is best to keep usage/operational data outside of
root - but it just historically so happened that this is how we do things.
So for now this is the task and I need to perform it somehow.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] a peculiar LVM failure on CentOS 6 run as a VMware 5.5 guest

[Boris Epstein]

Hello Leonard,

Thank you very much for your response.

While it most likely is related the problem description provided at the
link seems a bit vague, and tips on how to resolve the issue seem to be
even more so.

I have done some research and in the process stumbled upon this:

http://linoxide.com/linux-how-to/fixing-broken-initrd-image-linux/

The discussion there circled around using mkinitrd (as opposed to dracut
which in my case did not help).

So, while mounted off a Centos DVD ISO I chroot'ed into the root of my
installation on the disk and then ran the following:

mkinitrd /boot/initramfs-2.6.32-573.3.1.el6.x86_64.img 2.6.32-573.3.1

I saved the original content of
/boot/initramfs-2.6.32-573.3.1.el6.x86_64.img too. So now the problem is
resolved, and it is reproducible - it boots with the one I generated but
not with the original one which was the one that got there as a result of
an update.

I have not been able to see what the issue was with the original image.

Cheers,

Boris.


On Wed, Aug 26, 2015 at 9:47 AM, Leonard den Ottolander 
leon...@den.ottolander.nl wrote:

 Hello Boris,

 On Tue, 2015-08-25 at 15:59 -0400, Boris Epstein wrote:
  We have a Centos 6 VM (64 bit) running on a VMware vSphere 5.5 server. It
  was running just fine until one day I decided to reboot it and it just
  would not boot up. Effectively, dracut failed to initialize the LVM, much
  like under the scenario described here:
 
 
 http://unix.stackexchange.com/questions/207593/how-to-make-lvms-at-available-boot-kernel-panic-dracut-cannot-find-logical-vo#
 

 Perhaps this is related?
 https://rhn.redhat.com/errata/RHBA-2015-1615.html

 Prior to this update, using the lvm utility when the persistent cache
 file was
 outdated caused devices that were stored in the persistent cache to
 unintentionally bypass logical volume manager (LVM) filters set in the
 LVM
 configuration. As a consequence, Red Hat Enterprise Virtualization hosts
 in some
 cases failed to start with an outdated cache file. This update fixes
 LVM's
 internal cache handling so that the filters are applied properly, and
 the
 described problem no longer occurs. (BZ#1248032)

 Try updating LVM to the latest version and see if it helps.

 Regards,
 Leonard.

 --
 mount -t life -o ro /dev/dna /genetic/research


 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] a peculiar LVM failure on CentOS 6 run as a VMware 5.5 guest

[Boris Epstein]

Hello again,

Not sure I have this down 100% but it appears that the main LVM config file
( /etc/lvm/lvm.conf ) has been changed on August 13, 2015 on a number of
machines we have - all of them configured for automatic yum updates. So I
presume that could be a change that came as part an update - potentially
making the machine no longer bootable.

I am going to investigate this angle.

Boris.


On Tue, Aug 25, 2015 at 3:59 PM, Boris Epstein borepst...@gmail.com wrote:

 Hello listmates,

 I have encountered a rather peculiar situation.

 We have a Centos 6 VM (64 bit) running on a VMware vSphere 5.5 server. It
 was running just fine until one day I decided to reboot it and it just
 would not boot up. Effectively, dracut failed to initialize the LVM, much
 like under the scenario described here:


 http://unix.stackexchange.com/questions/207593/how-to-make-lvms-at-available-boot-kernel-panic-dracut-cannot-find-logical-vo#

 Following that I booted it off a Centos 6.6 install DVD in the rescue
 mode. It recognized the LVM partition without a glitch, booted it and
 seemed quite happy with it. having examined it, I discovered that, even
 though the root partition on the original VM was an LV it lacked the lvm2
 package. I installed it, but that did not help. So at the moment I am stuck.

 Hence if you can offer help on this one - please do, it will certainly be
 appreciated.

 Cheers,

 Boris.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] a peculiar LVM failure on CentOS 6 run as a VMware 5.5 guest

[Boris Epstein]

Hello listmates,

I have encountered a rather peculiar situation.

We have a Centos 6 VM (64 bit) running on a VMware vSphere 5.5 server. It
was running just fine until one day I decided to reboot it and it just
would not boot up. Effectively, dracut failed to initialize the LVM, much
like under the scenario described here:

http://unix.stackexchange.com/questions/207593/how-to-make-lvms-at-available-boot-kernel-panic-dracut-cannot-find-logical-vo#

Following that I booted it off a Centos 6.6 install DVD in the rescue mode.
It recognized the LVM partition without a glitch, booted it and seemed
quite happy with it. having examined it, I discovered that, even though the
root partition on the original VM was an LV it lacked the lvm2 package. I
installed it, but that did not help. So at the moment I am stuck.

Hence if you can offer help on this one - please do, it will certainly be
appreciated.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] iptables marking and NAT issue

[Boris Epstein]

Hello all,

It appears that, for some reason I have thus far failed to understand when
you use marking in iptables you then run into troubles if you attempt to do
NAT (MAQUERADE).

Let me describe this in more detail.

We are attempting to use a network test environment named ATCD running it
on a CentOS VM under VirtualBox. For more into on ATCD see:

https://github.com/facebook/augmented-traffic-control

The networking inside the VirtualBox environment is private so at some
point before you get out of it you've got to have a NAT router - not
necessarily on the same VM where the ATCD runs - which also is a router.

Be that as it may, ATCD uses a combination of iptables marking and tc to
degrade/control network transmission quality in accordance with your
settings. And it seems to work just fine up until you reach the NATing
router - at which point the transmission drops to very slow if not
non-existent.

An old article here makes a passing reference to a conflict between
iptables marking and MASQ (NAT):

http://tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.netfilter.html

Unfortunately, the link to another text supposedly detailing how to deal
with this is dead.

Has anybody encountered this? Any tips on how to fix this issue?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] unsetting/erasing an iptables mark

[Boris Epstein]

Hello all,

iptables provides a way to mark/tag packets for future
identification/accounting, etc. A brief discussion of it is offered here:

https://wiki.archlinux.org/index.php/Advanced_traffic_control

Here is a more detailed description of the issue I am working on:

http://lists.centos.org/pipermail/centos/2015-April/151245.html

Getting to the crux of the issue as it stands now.

I need to get rid of the mark on the packets after they have been processed
by tc and sent on. That can be done by a VM down the line, too.

Basic logic of the process should be: anything that comes with a mark,
erase that mark, send it on.

Effectively, going off this syntax:

iptables -A FORWARD -t mangle -i eth0 -j MARK --set-mark 6

I would need to be able to come up with something like --erase-mark or
functional equivalent thereof.

Any suggestions much appreciated.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] tc seems to have no effect on the NIC's

[Boris Epstein]

Hello all,

We have installed this network testing environment:

https://github.com/facebook/augmented-traffic-control

which seems pretty nice overall.

It allows you to artificially degrade your network performance by issuing
tc commands to directly affect your networking.

I have it set up on two CentOS 6 machines - one a Dell server, one a
VirtualBox VM. The tc syntax seems OK, it seems to all make sense - only it
seems to have no effect whatsoever on the actual network performance.

Hence the question: is there a known issue with tc? Am I perhaps missing
some kernel modules, or do I perhaps now have some kernel parameters set
correctly?

Any insight will be helpful.

Thanks in advance,

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] headless VirtualBox on Centos

[Boris Epstein]

Thanks Malcolm!

I am looking at using this one too.

Boris.

On Mon, Mar 30, 2015 at 2:04 AM, Malcolm fragbai...@gmail.com wrote:

 I use phpVirtualBox on my Centos 6 system.
 Works very well.

 http://sourceforge.net/projects/phpvirtualbox/ - A web-based front-end to
 VirtualBox written in PHP

 Cheers
 Mal


 On 27/03/15 13:33, Boris Epstein wrote:

 Hello listmates,

 I am wondering if there is a set of scripts/utilities for automatically
 starting and running headless (no X11) VM's using VirtualBox omn a CentOS
 6
 server. VNC/RDP access to the VM's would be fine.

 Any help much appreciated.

 Cheers,

 Boris.


 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] headless VirtualBox on Centos

[Boris Epstein]

Awesome!

Thanks for your replies everybody.

I was looking more or less at the same options. Just was wondering if there
was a ready-made set of scripts somewhere to set all of this in motion to
save me a little time - but if not, I will just make one.

Cheers,

Boris.


On Fri, Mar 27, 2015 at 3:16 AM, Александр Кириллов nevis...@infoline.su
wrote:

 I am wondering if there is a set of scripts/utilities for automatically
 starting and running headless (no X11) VM's using VirtualBox omn a CentOS
 6
 server. VNC/RDP access to the VM's would be fine.


 You can also get access to a headless VM console via RDP with VRDE (VBox
 Remote Desktop Extension) available from VBox Extension Pack.


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] headless VirtualBox on Centos

[Boris Epstein]

Hello listmates,

I am wondering if there is a set of scripts/utilities for automatically
starting and running headless (no X11) VM's using VirtualBox omn a CentOS 6
server. VNC/RDP access to the VM's would be fine.

Any help much appreciated.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VLAN issue

[Boris Epstein]

Gordon, thanks!

What sort of security implications did you have in mind? Just curious.

Boris.


On Mon, Jan 26, 2015 at 3:50 PM, Gordon Messmer gordon.mess...@gmail.com
wrote:

 On 01/25/2015 04:20 PM, Boris Epstein wrote:

 I have resolved this, finally. The problem was that I configured VLAN 48
 as
 the native VLAN on the trunk port.That was a mistake as apparently the
 native VLAN is the one where Cisco does not bother to tag packets.


 That's not a mistake, per se.  Having vlan 48 as the native vlan just
 means that you'd want 192.168.48.100 on eth0 instead of eth0.48.

  For now I set the native VLAN to VLAN 1 and that works.


 As long as you aren't concerned about the security implications of that
 host having access to vlan 1, that seems pretty reasonable.  The system
 will get some extra broadcast traffic, but the ethernet card will probably
 filter those out so that they don't have to be processed.

 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Linux client for Checkpoint VPN?

[Boris Epstein]

Hello all,

Does anybody know if there is a modern Linux client compatible with the
latest versions of Checkpoint VPN ( http://www.checkpoint.com/ )? They used
to have a Linux client back in the day but that seems to have been
discontinued.

Is anybody able to connect to a Checkpoint VPN server from their Linux
machine? If so please share the trick.

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VLAN issue

[Boris Epstein]

Stephen,

That is right - it is not on a trunk port. I guess this must be it.

Thanks.

Boris.


On Sun, Jan 25, 2015 at 9:25 AM, Stephen Harris li...@spuddy.org wrote:

 On Sun, Jan 25, 2015 at 09:12:29AM -0500, Boris Epstein wrote:
  OK... but why does it need to be a trunk port?

 If you are on a trunk port then your machine needs to be configured
 for VLANs.  If you are not on a trunk port then your machine needs
 to be configured normally.

 It _sounds_ like you have configured your machine for VLANs but are not
 on a trunk port.

 --

 rgds
 Stephen
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VLAN issue

[Boris Epstein]

OK... but why does it need to be a trunk port?

Boris.

On Sat, Jan 24, 2015 at 6:53 PM, SilverTip257 silvertip...@gmail.com
wrote:

 Andrew and Dennis are spot on.
 Their conclusions about your server being connected to an access port and
 not a trunk port would be my conclusion as well.

 On Sat, Jan 24, 2015 at 9:11 AM, Dennis Jacobfeuerborn 
 denni...@conversis.de wrote:

  Hi Boris,
  what I'd like to know is the actual VLAN configuration of the switch
  port (link-type and tagged and untagged VLANs). When I look at the
  switchport coniguration here I get (among other things):
 
  ...
   Port link-type: trunk
Tagged   VLAN ID : 8, 1624
Untagged VLAN ID : 10
  ...
 
  Here is my suspicion:
  Your ports have an access link-type with an untagged VLAN ID of 48. That
  would explain why the moment you configure an IP from that VLAN on eth0
  you get connectivity because then the packets the Linux box sends are
  untagged as the switch would expect them to be. If you only put an
  address on eth0.48 then the packets get tagged by Linux but if the
  switch port is not configured to receive the packets for VLAN 48 as
  tagged then it will simply drop these packets and you will not get
  connectivity.
 

 Additionally, the switch should gripe about 802.1q BPDUs.
 Check the in-memory system log (or syslog server if you have configured
 that).

 show logging | i 1Q

 Example:
 1w1d: %SPANTREE-2-RECV_1Q_NON_TRUNK:
 Received 802.1Q BPDU on non trunk FastEthernet0/2 on vlan 100.


 
  So getting the actual VLAN config of the switch port would help to
  determine if the switch actually expects to receive the packets the way
  you send them from the Linux box.
 
 
 +1
 Let's see the config for the switch port your server is connected to.

 --
 ---~~.~~---
 Mike
 //  SilverTip257  //
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VLAN issue

[Boris Epstein]

Thank you everyone.

OK, the mystery deepens, I guess. The machine does need to support several
VLAN's, it is currently on a trunkport (8021q encapsulated), it made it
into the ARP table - which I specifically tested for by physically
unplugging the table, clearing the ARP table and plugging it back in.

The ARP table currently looks like this:

hq#show arp
Protocol  Address  Age (min)  Hardware Addr   Type   Interface
Internet  192.168.48.100  0   0025.6440.0301  ARPA   Vlan48
Internet  192.168.48.101  -   001b.906a.bcc4  ARPA   Vlan48
Internet  192.168.48.10   0025.6440.063f  ARPA   Vlan48
Internet  192.168.2.520   0025.6440.0547  ARPA   Vlan2
Internet  192.168.3.1 -   001b.906a.bcc2  ARPA   Vlan3
Internet  192.168.2.1 -   001b.906a.bcc1  ARPA   Vlan2
Internet  192.168.7.1 -   001b.906a.bcc3  ARPA   Vlan7
hq#

The network config on the machine currently looks like this: it has nothing
assigned to eth0, eth0.48 = 192.168.48.100/24, eth0.49 = 192.168.49.100/24,
eth0.50 = 192.168.50.100/24.

And - even though the ARP table seems to be OK - there is no connectivity!

Boris.



On Sun, Jan 25, 2015 at 11:42 AM, Les Mikesell lesmikes...@gmail.com
wrote:

 On Sun, Jan 25, 2015 at 8:38 AM, Andrew Holway andrew.hol...@gmail.com
 wrote:
  On 25 January 2015 at 15:12, Boris Epstein borepst...@gmail.com wrote:
 
  OK... but why does it need to be a trunk port?
 
 
  Because a trunk port will trunk the vlan.
 
  A VLAN is basically a 4 byte tag that gets injected into the packet
  header when the packet enters the VLAN network. When we trunk a VLAN we
 say
  to the switch pass packets on VLAN x but do not strip the tag out.
 
  You can either terminate the VLAN at the switch port (untagged) which
 will
  strip out the VLAN tag or you can pass the packet containing the VLAN tag
  to the computer or other device(tagged/trunk). This device can then pull
  out the tag. On linux this mechanism is done by an 8021q VLAN interface.
 
  Hope this is useful.
 

 Just to add to that - normally if a host only needs to be on one
 subnet you would use an access port on the switch to select a single
 vlan and deliver those packets untagged so the host does not need to
 care about tags or vlan numbers.   And to that end, switches default
 to treating everything as access ports on native/untagged vlan 0
 unless configured otherwise.   However, if the host needs interfaces
 on multiple subnets, you can do it on a single network connection by
 giving it a trunk connection from the switch and letting it split out
 the vlan interfaces internally.

 --
Les Mikesell
   lesmikes...@gmail.com
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VLAN issue

[Boris Epstein]

And additionally here are the detailed port configs on the switch end:

hqshow interface Gi1/0/3 switchport
Name: Gi1/0/3
Switchport: Enabled
Administrative Mode: trunk
Operational Mode: trunk
Administrative Trunking Encapsulation: dot1q
Operational Trunking Encapsulation: dot1q
Negotiation of Trunking: On
Access Mode VLAN: 48 (VLAN0048)
Trunking Native Mode VLAN: 48 (VLAN0048)
Administrative Native VLAN tagging: enabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations: none
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL

Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Appliance trust: none
hqshow interface Gi1/0/3 trunk

PortMode Encapsulation  StatusNative vlan
Gi1/0/3 on   802.1q trunking  48

PortVlans allowed on trunk
Gi1/0/3 1-4094

PortVlans allowed and active in management domain
Gi1/0/3 1-3,7,48-50

PortVlans in spanning tree forwarding state and not pruned
Gi1/0/3 1-3,7,48-50
hq

Boris.

On Sun, Jan 25, 2015 at 7:05 PM, Boris Epstein borepst...@gmail.com wrote:

 Thank you everyone.

 OK, the mystery deepens, I guess. The machine does need to support several
 VLAN's, it is currently on a trunkport (8021q encapsulated), it made it
 into the ARP table - which I specifically tested for by physically
 unplugging the table, clearing the ARP table and plugging it back in.

 The ARP table currently looks like this:

 hq#show arp
 Protocol  Address  Age (min)  Hardware Addr   Type   Interface
 Internet  192.168.48.100  0   0025.6440.0301  ARPA   Vlan48
 Internet  192.168.48.101  -   001b.906a.bcc4  ARPA   Vlan48
 Internet  192.168.48.10   0025.6440.063f  ARPA   Vlan48
 Internet  192.168.2.520   0025.6440.0547  ARPA   Vlan2
 Internet  192.168.3.1 -   001b.906a.bcc2  ARPA   Vlan3
 Internet  192.168.2.1 -   001b.906a.bcc1  ARPA   Vlan2
 Internet  192.168.7.1 -   001b.906a.bcc3  ARPA   Vlan7
 hq#

 The network config on the machine currently looks like this: it has
 nothing assigned to eth0, eth0.48 = 192.168.48.100/24, eth0.49 =
 192.168.49.100/24, eth0.50 = 192.168.50.100/24.

 And - even though the ARP table seems to be OK - there is no connectivity!

 Boris.



 On Sun, Jan 25, 2015 at 11:42 AM, Les Mikesell lesmikes...@gmail.com
 wrote:

 On Sun, Jan 25, 2015 at 8:38 AM, Andrew Holway andrew.hol...@gmail.com
 wrote:
  On 25 January 2015 at 15:12, Boris Epstein borepst...@gmail.com
 wrote:
 
  OK... but why does it need to be a trunk port?
 
 
  Because a trunk port will trunk the vlan.
 
  A VLAN is basically a 4 byte tag that gets injected into the packet
  header when the packet enters the VLAN network. When we trunk a VLAN we
 say
  to the switch pass packets on VLAN x but do not strip the tag out.
 
  You can either terminate the VLAN at the switch port (untagged) which
 will
  strip out the VLAN tag or you can pass the packet containing the VLAN
 tag
  to the computer or other device(tagged/trunk). This device can then pull
  out the tag. On linux this mechanism is done by an 8021q VLAN interface.
 
  Hope this is useful.
 

 Just to add to that - normally if a host only needs to be on one
 subnet you would use an access port on the switch to select a single
 vlan and deliver those packets untagged so the host does not need to
 care about tags or vlan numbers.   And to that end, switches default
 to treating everything as access ports on native/untagged vlan 0
 unless configured otherwise.   However, if the host needs interfaces
 on multiple subnets, you can do it on a single network connection by
 giving it a trunk connection from the switch and letting it split out
 the vlan interfaces internally.

 --
Les Mikesell
   lesmikes...@gmail.com
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VLAN issue

[Boris Epstein]

OK, thanks again for all your help.

I have resolved this, finally. The problem was that I configured VLAN 48 as
the native VLAN on the trunk port.That was a mistake as apparently the
native VLAN is the one where Cisco does not bother to tag packets.

For now I set the native VLAN to VLAN 1 and that works.

Cheers,

Boris.


On Sun, Jan 25, 2015 at 7:13 PM, Boris Epstein borepst...@gmail.com wrote:

 And additionally here are the detailed port configs on the switch end:

 hqshow interface Gi1/0/3 switchport
 Name: Gi1/0/3
 Switchport: Enabled
 Administrative Mode: trunk
 Operational Mode: trunk
 Administrative Trunking Encapsulation: dot1q
 Operational Trunking Encapsulation: dot1q
 Negotiation of Trunking: On
 Access Mode VLAN: 48 (VLAN0048)
 Trunking Native Mode VLAN: 48 (VLAN0048)
 Administrative Native VLAN tagging: enabled
 Voice VLAN: none
 Administrative private-vlan host-association: none
 Administrative private-vlan mapping: none
 Administrative private-vlan trunk native VLAN: none
 Administrative private-vlan trunk Native VLAN tagging: enabled
 Administrative private-vlan trunk encapsulation: dot1q
 Administrative private-vlan trunk normal VLANs: none
 Administrative private-vlan trunk associations: none
 Administrative private-vlan trunk mappings: none
 Operational private-vlan: none
 Trunking VLANs Enabled: ALL
 Pruning VLANs Enabled: 2-1001
 Capture Mode Disabled
 Capture VLANs Allowed: ALL

 Protected: false
 Unknown unicast blocked: disabled
 Unknown multicast blocked: disabled
 Appliance trust: none
 hqshow interface Gi1/0/3 trunk

 PortMode Encapsulation  StatusNative vlan
 Gi1/0/3 on   802.1q trunking  48

 PortVlans allowed on trunk
 Gi1/0/3 1-4094

 PortVlans allowed and active in management domain
 Gi1/0/3 1-3,7,48-50

 PortVlans in spanning tree forwarding state and not pruned
 Gi1/0/3 1-3,7,48-50
 hq

 Boris.

 On Sun, Jan 25, 2015 at 7:05 PM, Boris Epstein borepst...@gmail.com
 wrote:

 Thank you everyone.

 OK, the mystery deepens, I guess. The machine does need to support
 several VLAN's, it is currently on a trunkport (8021q encapsulated), it
 made it into the ARP table - which I specifically tested for by physically
 unplugging the table, clearing the ARP table and plugging it back in.

 The ARP table currently looks like this:

 hq#show arp
 Protocol  Address  Age (min)  Hardware Addr   Type   Interface
 Internet  192.168.48.100  0   0025.6440.0301  ARPA   Vlan48
 Internet  192.168.48.101  -   001b.906a.bcc4  ARPA   Vlan48
 Internet  192.168.48.10   0025.6440.063f  ARPA   Vlan48
 Internet  192.168.2.520   0025.6440.0547  ARPA   Vlan2
 Internet  192.168.3.1 -   001b.906a.bcc2  ARPA   Vlan3
 Internet  192.168.2.1 -   001b.906a.bcc1  ARPA   Vlan2
 Internet  192.168.7.1 -   001b.906a.bcc3  ARPA   Vlan7
 hq#

 The network config on the machine currently looks like this: it has
 nothing assigned to eth0, eth0.48 = 192.168.48.100/24, eth0.49 =
 192.168.49.100/24, eth0.50 = 192.168.50.100/24.

 And - even though the ARP table seems to be OK - there is no connectivity!

 Boris.



 On Sun, Jan 25, 2015 at 11:42 AM, Les Mikesell lesmikes...@gmail.com
 wrote:

 On Sun, Jan 25, 2015 at 8:38 AM, Andrew Holway andrew.hol...@gmail.com
 wrote:
  On 25 January 2015 at 15:12, Boris Epstein borepst...@gmail.com
 wrote:
 
  OK... but why does it need to be a trunk port?
 
 
  Because a trunk port will trunk the vlan.
 
  A VLAN is basically a 4 byte tag that gets injected into the packet
  header when the packet enters the VLAN network. When we trunk a VLAN
 we say
  to the switch pass packets on VLAN x but do not strip the tag out.
 
  You can either terminate the VLAN at the switch port (untagged) which
 will
  strip out the VLAN tag or you can pass the packet containing the VLAN
 tag
  to the computer or other device(tagged/trunk). This device can then
 pull
  out the tag. On linux this mechanism is done by an 8021q VLAN
 interface.
 
  Hope this is useful.
 

 Just to add to that - normally if a host only needs to be on one
 subnet you would use an access port on the switch to select a single
 vlan and deliver those packets untagged so the host does not need to
 care about tags or vlan numbers.   And to that end, switches default
 to treating everything as access ports on native/untagged vlan 0
 unless configured otherwise.   However, if the host needs interfaces
 on multiple subnets, you can do it on a single network connection by
 giving it a trunk connection from the switch and letting it split out
 the vlan interfaces internally.

 --
Les Mikesell
   lesmikes...@gmail.com
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos




___
CentOS mailing list
CentOS@centos.org
http

Re: [CentOS] VLAN issue

[Boris Epstein]

Do you need the whole configuration? On the switch end, we have the
relevant VLAN (VLAN 48) with the assigned IP address of 192.168.48.101 and
the range of ports (Gi1/0/1 - Gi1/0/8) assigned to that VLAN.

Seems - and acts - like a legitimate setup and works fine, except for this
particular instance.

Thanks.

Boris.

On Fri, Jan 23, 2015 at 8:54 PM, Dennis Jacobfeuerborn 
denni...@conversis.de wrote:

 We have lots of servers with a similar setup (i.e. tagged vlans and no
 ip on eth0) and this works just fine.

 What is the actual vlan configuration on your switchport?

 Regards,
   Dennis

 On 24.01.2015 01:34, Boris Epstein wrote:
  Steve,
 
  Thanks, makes sense.
 
  I just don't see why I have to effectively waste an extra IP address to
 get
  my connection established.
 
  Boris.
 
 
  On Fri, Jan 23, 2015 at 7:16 PM, Stephen Harris li...@spuddy.org
 wrote:
 
  On Fri, Jan 23, 2015 at 07:10:57PM -0500, Boris Epstein wrote:
 
  This makes two of us. I've done everything as you have described and it
  simply does not work.
 
  Are you actually seeing VLAN tagged traffic, or is the cisco switch
  just providing a normal stream?
 
  At work we have hundreds of VLANs, but the servers don't get configured
  for this; we just configure them as normal; ie eth0.  The network
  infrastructure does the VLAN decoding, the server doesn't have to.
 
  Try configuring the machine as if it was a real LAN and forget about
  the VLAN.
 
  If that doesn't work then what does 'tcpdump -i eth0' show you?
 
  --
 
  rgds
  Stephen
  ___
  CentOS mailing list
  CentOS@centos.org
  http://lists.centos.org/mailman/listinfo/centos
 
  ___
  CentOS mailing list
  CentOS@centos.org
  http://lists.centos.org/mailman/listinfo/centos
 

 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] VLAN issue

[Boris Epstein]

Hello all,

I have a machine running Centos 6.6 connected to a port on a Cisco Catalyst
3750 series switch. That port is part of VLAN 48. I have VLAN 48 on the
CentOS machine too.

The IP network on VLAN 48 is 192.168.48.0/255.255.255.0. The address on the
CentOS side is 192.168.48.101, the address on the Linux end ought to be
192.168.48.100.

When I only bring up eth0.48 VLAN device with the IP=192.168.48.100 I have
no connectivity. If I bring it up along with eth0 with another VLAN 48
address assigned to it (for instance, 192.168.48.99) I do have connectivity.

Also, strangely enough, sometimes to get things going I have to disconnect
the Linux host from the switch - physically detach the wire and reconnect
it again.

Be that as it may when I just bring up the VLAN by itself I have thus far
been unable to get anywhere.

Has anybody seen a situation like this? Does anybody have an explaination
for it?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VLAN issue

[Boris Epstein]

Steve,

Thanks, makes sense.

I just don't see why I have to effectively waste an extra IP address to get
my connection established.

Boris.


On Fri, Jan 23, 2015 at 7:16 PM, Stephen Harris li...@spuddy.org wrote:

 On Fri, Jan 23, 2015 at 07:10:57PM -0500, Boris Epstein wrote:

  This makes two of us. I've done everything as you have described and it
  simply does not work.

 Are you actually seeing VLAN tagged traffic, or is the cisco switch
 just providing a normal stream?

 At work we have hundreds of VLANs, but the servers don't get configured
 for this; we just configure them as normal; ie eth0.  The network
 infrastructure does the VLAN decoding, the server doesn't have to.

 Try configuring the machine as if it was a real LAN and forget about
 the VLAN.

 If that doesn't work then what does 'tcpdump -i eth0' show you?

 --

 rgds
 Stephen
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VLAN issue

[Boris Epstein]

Less,

You are 100% right. Of course I brought up my eth0 - but, like you said,
with no IP. Meanwhile, I brought up eth0.48 with 192.168.48.100.

However, until I would bring up eth0 with an IP address (any in the
network) I would have no connection. Why? That's what I fail to understand.

Boris.

On Fri, Jan 23, 2015 at 6:45 PM, Les Mikesell lesmikes...@gmail.com wrote:

 On Fri, Jan 23, 2015 at 5:27 PM, Boris Epstein borepst...@gmail.com
 wrote:
  Hello all,
 
  I have a machine running Centos 6.6 connected to a port on a Cisco
 Catalyst
  3750 series switch. That port is part of VLAN 48. I have VLAN 48 on the
  CentOS machine too.
 
  The IP network on VLAN 48 is 192.168.48.0/255.255.255.0. The address on
 the
  CentOS side is 192.168.48.101, the address on the Linux end ought to be
  192.168.48.100.
 
  When I only bring up eth0.48 VLAN device with the IP=192.168.48.100 I
 have
  no connectivity. If I bring it up along with eth0 with another VLAN 48
  address assigned to it (for instance, 192.168.48.99) I do have
 connectivity.
 
  Also, strangely enough, sometimes to get things going I have to
 disconnect
  the Linux host from the switch - physically detach the wire and reconnect
  it again.
 
  Be that as it may when I just bring up the VLAN by itself I have thus far
  been unable to get anywhere.
 
  Has anybody seen a situation like this? Does anybody have an explaination
  for it?

 I think you always have  to bring up the underlying eth device to
 activate a related eth.nn vlan.  The base device would not normally
 have an IPADDR, though, unless it is for an untagged vlan 0.
 Assuming the connected switch port is configured as a trunk, you
 shouldn't see vlan 48 addresses on the base (untagged) device.

 --
Les Mikesell
  lesmikes...@gmail.com
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] VLAN issue

[Boris Epstein]

On Fri, Jan 23, 2015 at 7:02 PM, Les Mikesell lesmikes...@gmail.com wrote:

 On Fri, Jan 23, 2015 at 5:48 PM, Boris Epstein borepst...@gmail.com
 wrote:
  Less,
 
  You are 100% right. Of course I brought up my eth0 - but, like you said,
  with no IP. Meanwhile, I brought up eth0.48 with 192.168.48.100.
 
  However, until I would bring up eth0 with an IP address (any in the
  network) I would have no connection. Why? That's what I fail to
 understand.

 Doesn't make sense to me - I think I've done it both ways
 (with/without a vlan 0 address).  I didn't think it took anything
 special except the VLAN=yes in the file and the .number in the DEVICE=
 (and file) name.

 --
   Les Mikesell
 lesmikes...@gmail.com



This makes two of us. I've done everything as you have described and it
simply does not work.

Boris.




 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] DJBDNS: very weird dnscache issue

[Boris Epstein]

We did - we got in touch with the owner of the package and are trying to
get him to work on it.

Cheers,

Boris.

On Thu, Jan 15, 2015 at 6:51 PM, Nux! n...@li.nux.ro wrote:

 Thanks for getting back with the solution.
 You might want to give that bugzilla entry a jolt, it's been stagnating
 since last year. :-)

 Lucian

 --
 Sent from the Delta quadrant using Borg technology!

 Nux!
 www.nux.ro

 - Original Message -
  From: Boris Epstein borepst...@gmail.com
  To: CentOS mailing list centos@centos.org
  Sent: Wednesday, 14 January, 2015 18:47:17
  Subject: Re: [CentOS] DJBDNS: very weird dnscache issue

  Lucian,
 
  So far here is the best we could find out:
 
  https://bugzilla.redhat.com/show_bug.cgi?id=1084747
 
  Testing to see if this is the solution; so far it seems to be.
 
  Cheers,
 
  Boris.
 
 
  On Tue, Jan 13, 2015 at 2:49 PM, Nux! n...@li.nux.ro wrote:
 
  Use BIND. How the times have changed. :-)
 
  PS: I'm also curious for a solution.. for when djbnostalgia hits me.
 
  Lucian
 
  --
  Sent from the Delta quadrant using Borg technology!
 
  Nux!
  www.nux.ro
 
  - Original Message -
   From: Boris Epstein borepst...@gmail.com
   To: CentOS mailing list centos@centos.org
   Sent: Tuesday, 13 January, 2015 15:53:28
   Subject: [CentOS] DJBDNS: very weird dnscache issue
 
   Hello all,
  
   We have put a DNS server online running  DJBDNS v1.06
   (ndjbdns-1.06-1.el6.x86_64) on a 64-bit CentOS 6.6 server. We have
 done
   some limited testing on the machine which it passed - i.e., dnscache
 was
   talking to tinydns, the queries went through fine, etc.
  
   As soon as we put it online subjecting it to live load the following
   happened:
  
   1) Within a short time period (about a minute) the dnscache process
  reached
   the CPU utilisation level of 100%.
  
   2) The process would then die reporting the following message to the
 log:
  
   dnscache: BUG: out of in progress slots
  
   NOTE: Random sampling indicates that at no point sampled did the load
   exceed 200 requests per second. In tests conducted earlier the DNS
 server
   successfully demonstrated speeds in tens of thousands of requests per
   second.
  
   We then proceeded to edit the following parameters in the
 dnscache.conf
  as
   they seemed to be the only ones that seemed relevant: DATALIMIT and
   CACHESIZE. They are described as limints (in bytes) on the total data
   memory allocation and cache, default values are 8000 and 5000
   respectively.
  
   Playing with these demonstrated some highly counterintuitive results:
  
   1) Setting the values lower (say, an order of magnitude lower) made
 the
   dnscache process run longer.
  
   2) Shortening the relative gap between the two values (for instance,
   setting DATALIMIT at 52000 and CACHE at 5) made it run for about
 an
   hour vs about 1 minute, load seeming to be about the same.
  
   3) Running it with DATALIMIT not set was possible though it eventually
   failed anyways.
  
   4) Running it with CACHESIZE not set was not possible at all.
  
   So the issue is currently still not resolved and we are stuck.
  
   Any advice will be much appreciated.
  
   Cheers,
  
   Boris.
   ___
   CentOS mailing list
   CentOS@centos.org
   http://lists.centos.org/mailman/listinfo/centos
  ___
  CentOS mailing list
  CentOS@centos.org
  http://lists.centos.org/mailman/listinfo/centos
 
  ___
  CentOS mailing list
  CentOS@centos.org
  http://lists.centos.org/mailman/listinfo/centos
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] DJBDNS: very weird dnscache issue

[Boris Epstein]

Lucian,

So far here is the best we could find out:

https://bugzilla.redhat.com/show_bug.cgi?id=1084747

Testing to see if this is the solution; so far it seems to be.

Cheers,

Boris.


On Tue, Jan 13, 2015 at 2:49 PM, Nux! n...@li.nux.ro wrote:

 Use BIND. How the times have changed. :-)

 PS: I'm also curious for a solution.. for when djbnostalgia hits me.

 Lucian

 --
 Sent from the Delta quadrant using Borg technology!

 Nux!
 www.nux.ro

 - Original Message -
  From: Boris Epstein borepst...@gmail.com
  To: CentOS mailing list centos@centos.org
  Sent: Tuesday, 13 January, 2015 15:53:28
  Subject: [CentOS] DJBDNS: very weird dnscache issue

  Hello all,
 
  We have put a DNS server online running  DJBDNS v1.06
  (ndjbdns-1.06-1.el6.x86_64) on a 64-bit CentOS 6.6 server. We have done
  some limited testing on the machine which it passed - i.e., dnscache was
  talking to tinydns, the queries went through fine, etc.
 
  As soon as we put it online subjecting it to live load the following
  happened:
 
  1) Within a short time period (about a minute) the dnscache process
 reached
  the CPU utilisation level of 100%.
 
  2) The process would then die reporting the following message to the log:
 
  dnscache: BUG: out of in progress slots
 
  NOTE: Random sampling indicates that at no point sampled did the load
  exceed 200 requests per second. In tests conducted earlier the DNS server
  successfully demonstrated speeds in tens of thousands of requests per
  second.
 
  We then proceeded to edit the following parameters in the dnscache.conf
 as
  they seemed to be the only ones that seemed relevant: DATALIMIT and
  CACHESIZE. They are described as limints (in bytes) on the total data
  memory allocation and cache, default values are 8000 and 5000
  respectively.
 
  Playing with these demonstrated some highly counterintuitive results:
 
  1) Setting the values lower (say, an order of magnitude lower) made the
  dnscache process run longer.
 
  2) Shortening the relative gap between the two values (for instance,
  setting DATALIMIT at 52000 and CACHE at 5) made it run for about an
  hour vs about 1 minute, load seeming to be about the same.
 
  3) Running it with DATALIMIT not set was possible though it eventually
  failed anyways.
 
  4) Running it with CACHESIZE not set was not possible at all.
 
  So the issue is currently still not resolved and we are stuck.
 
  Any advice will be much appreciated.
 
  Cheers,
 
  Boris.
  ___
  CentOS mailing list
  CentOS@centos.org
  http://lists.centos.org/mailman/listinfo/centos
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] DJBDNS: very weird dnscache issue

[Boris Epstein]

Hello all,

We have put a DNS server online running  DJBDNS v1.06
(ndjbdns-1.06-1.el6.x86_64) on a 64-bit CentOS 6.6 server. We have done
some limited testing on the machine which it passed - i.e., dnscache was
talking to tinydns, the queries went through fine, etc.

As soon as we put it online subjecting it to live load the following
happened:

1) Within a short time period (about a minute) the dnscache process reached
the CPU utilisation level of 100%.

2) The process would then die reporting the following message to the log:

dnscache: BUG: out of in progress slots

NOTE: Random sampling indicates that at no point sampled did the load
exceed 200 requests per second. In tests conducted earlier the DNS server
successfully demonstrated speeds in tens of thousands of requests per
second.

We then proceeded to edit the following parameters in the dnscache.conf as
they seemed to be the only ones that seemed relevant: DATALIMIT and
CACHESIZE. They are described as limints (in bytes) on the total data
memory allocation and cache, default values are 8000 and 5000
respectively.

Playing with these demonstrated some highly counterintuitive results:

1) Setting the values lower (say, an order of magnitude lower) made the
dnscache process run longer.

2) Shortening the relative gap between the two values (for instance,
setting DATALIMIT at 52000 and CACHE at 5) made it run for about an
hour vs about 1 minute, load seeming to be about the same.

3) Running it with DATALIMIT not set was possible though it eventually
failed anyways.

4) Running it with CACHESIZE not set was not possible at all.

So the issue is currently still not resolved and we are stuck.

Any advice will be much appreciated.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] open-vm-tools on CentOS 6

[Boris Epstein]

Hello all,

As far as which VMWare tools to use - the ones from VM Ware or the
open-vm-tools available through the EPEL - is there any consensus on what
is better? I know that for CentOS 7 you are told to use open-vm-tools but
what is the situation with CentOS 6?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] open-vm-tools on CentOS 6

[Boris Epstein]

On Fri, Nov 7, 2014 at 1:11 PM, Reindl Harald h.rei...@thelounge.net
wrote:


 Am 07.11.2014 um 19:05 schrieb Boris Epstein:

  As far as which VMWare tools to use - the ones from VM Ware or the
 open-vm-tools available through the EPEL - is there any consensus on what
 is better? I know that for CentOS 7 you are told to use open-vm-tools but
 what is the situation with CentOS 6?


 open-vm-tools worked fine even with Fedora 9 in 2008
 that was long before RHEL6 existed at all


Reindl,

Thanks, that is good to know. However, aside from proving that there is
some history to the open-vm-tools this really doesn't reflect on the
compatibility of the current version.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] tinydns exceeds holdoff time on startup under CentOS 7

[Boris Epstein]

Hello listmates,

Somehow or other my DNS services that are part of
the ndjbdns-1.06-1.el7.x86_64 package would not start properly at startup.
When I then start them up using systemctl:

systemctl start dnscache
systemctl start tinydns

they start just fine.

From the log I got the following for tinydns:

Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: version 1.06: starting: Oct-24
2014 15:01:43 EDT
Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: DEBUG_LEVEL set to `1'
Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: DATALIMIT set to `30' bytes
Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: could not bind UDP socket
Oct 24 15:01:43 ns99 systemd[1]: tinydns.service holdoff time over,
scheduling restart.

Any idea why that would happen? Any idea how to increase the holdoff time
in the configuration?

The config for the service looks as follows:

[root@ns99 etc]# more /usr/lib/systemd/system/tinydns.service
[Unit]
Description=A DNS server daemon
Documentation=man:tinydns(8)
Requires=network.target
After=network.target

[Service]
Restart=always
PIDFile=/var/run/tinydns.pid
ExecStart=/usr/sbin/tinydns

[Install]
WantedBy=multi-user.target
[root@ns99 etc]#

I can't possibly spot anything wrong there.

Any help much appreciated.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] tinydns exceeds holdoff time on startup under CentOS 7

[Boris Epstein]

Hello again,

I think I have resolved this issue by adding the following line to my
relevant service startup files:

RestartSec=60s

I presume the line forces a restart within 60 seconds (or with the time
allowance of 60 seconds). Actually according to this source:

http://www.dsm.fordham.edu/cgi-bin/man-cgi.pl?topic=systemd.serviceampsect=5

it is the former - the sleep time before attempting a restart.

I put the line directly below the Restart=... line. See
my dnscache.service for example:

[root@ns99 system]# more /usr/lib/systemd/system/dnscache.service
[Unit]
Description=An iterative DNS resolver daemon
Documentation=man:dnscache(8)
Requires=network.target
After=network.target

[Service]
Restart=always
RestartSec=60s
PIDFile=/var/run/dnscache.pid
ExecStart=/usr/sbin/dnscache

[Install]
WantedBy=multi-user.target
[root@ns99 system]#

Cheers,

Boris.



On Mon, Oct 27, 2014 at 2:26 PM, Boris Epstein borepst...@gmail.com wrote:

 Hello listmates,

 Somehow or other my DNS services that are part of
 the ndjbdns-1.06-1.el7.x86_64 package would not start properly at startup.
 When I then start them up using systemctl:

 systemctl start dnscache
 systemctl start tinydns

 they start just fine.

 From the log I got the following for tinydns:

 Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: version 1.06: starting:
 Oct-24 2014 15:01:43 EDT
 Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: DEBUG_LEVEL set to `1'
 Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: DATALIMIT set to `30'
 bytes
 Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: could not bind UDP socket
 Oct 24 15:01:43 ns99 systemd[1]: tinydns.service holdoff time over,
 scheduling restart.

 Any idea why that would happen? Any idea how to increase the holdoff time
 in the configuration?

 The config for the service looks as follows:

 [root@ns99 etc]# more /usr/lib/systemd/system/tinydns.service
 [Unit]
 Description=A DNS server daemon
 Documentation=man:tinydns(8)
 Requires=network.target
 After=network.target

 [Service]
 Restart=always
 PIDFile=/var/run/tinydns.pid
 ExecStart=/usr/sbin/tinydns

 [Install]
 WantedBy=multi-user.target
 [root@ns99 etc]#

 I can't possibly spot anything wrong there.

 Any help much appreciated.

 Cheers,

 Boris.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] tinydns exceeds holdoff time on startup under CentOS 7

[Boris Epstein]

OK, on the second take, even 5 seconds has proved to be enough of a sleep
period in my case.

Just FYI.

Boris.

On Mon, Oct 27, 2014 at 4:07 PM, Boris Epstein borepst...@gmail.com wrote:

 Hello again,

 I think I have resolved this issue by adding the following line to my
 relevant service startup files:

 RestartSec=60s

 I presume the line forces a restart within 60 seconds (or with the time
 allowance of 60 seconds). Actually according to this source:


 http://www.dsm.fordham.edu/cgi-bin/man-cgi.pl?topic=systemd.serviceampsect=5

 it is the former - the sleep time before attempting a restart.

 I put the line directly below the Restart=... line. See
 my dnscache.service for example:

 [root@ns99 system]# more /usr/lib/systemd/system/dnscache.service
 [Unit]
 Description=An iterative DNS resolver daemon
 Documentation=man:dnscache(8)
 Requires=network.target
 After=network.target

 [Service]
 Restart=always
 RestartSec=60s
 PIDFile=/var/run/dnscache.pid
 ExecStart=/usr/sbin/dnscache

 [Install]
 WantedBy=multi-user.target
 [root@ns99 system]#

 Cheers,

 Boris.



 On Mon, Oct 27, 2014 at 2:26 PM, Boris Epstein borepst...@gmail.com
 wrote:

 Hello listmates,

 Somehow or other my DNS services that are part of
 the ndjbdns-1.06-1.el7.x86_64 package would not start properly at startup.
 When I then start them up using systemctl:

 systemctl start dnscache
 systemctl start tinydns

 they start just fine.

 From the log I got the following for tinydns:

 Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: version 1.06: starting:
 Oct-24 2014 15:01:43 EDT
 Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: DEBUG_LEVEL set to `1'
 Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: DATALIMIT set to `30'
 bytes
 Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: could not bind UDP socket
 Oct 24 15:01:43 ns99 systemd[1]: tinydns.service holdoff time over,
 scheduling restart.

 Any idea why that would happen? Any idea how to increase the holdoff time
 in the configuration?

 The config for the service looks as follows:

 [root@ns99 etc]# more /usr/lib/systemd/system/tinydns.service
 [Unit]
 Description=A DNS server daemon
 Documentation=man:tinydns(8)
 Requires=network.target
 After=network.target

 [Service]
 Restart=always
 PIDFile=/var/run/tinydns.pid
 ExecStart=/usr/sbin/tinydns

 [Install]
 WantedBy=multi-user.target
 [root@ns99 etc]#

 I can't possibly spot anything wrong there.

 Any help much appreciated.

 Cheers,

 Boris.



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] IP aliasing on CentOS 7

[Boris Epstein]

Hello all,

Thank you for all the great responses.

I meant to reply earlier but it slipped my mind. Sorry.

OK, so according to my experience here is what seems to work.

1) nmtui
Using this utility one can do that without delving into the nitty-gritty,
it seems.

2) By editing the config file. So let us say we have the NIC eno16780032 If
you now edit your config file
( /etc/sysconfig/network-scripts/ifcfg-eno16780032 ) to look like this
--
TYPE=Ethernet
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=eno16780032
UUID=f303271a-dc5c-4fd6-ac61-73c7b78a5b2b
ONBOOT=yes
DNS1=10.1.3.5
DOMAIN=insideidc.com
IPADDR1=10.1.3.226
PREFIX1=24
HWADDR=00:50:56:A6:11:CA
IPADDR=10.1.3.220
PREFIX=24
GATEWAY=10.1.3.10
DNS2=10.1.3.1
DNS3=10.1.3.2
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
--

you are going to have two IP addresses (in this scenario, 10.1.3.220 and
10.1.3.226) assigned to the same NIC.

NOTICE: ifconfig will not show them all, use ip a show to see them.

Once again, thank you all for responding.

Cheers,

Boris.


On Wed, Oct 15, 2014 at 5:12 PM, Boris Epstein borepst...@gmail.com wrote:

 Hello all,

 is there a good wirte-up on how edit script files in
 the /etc/sysconfig/network-scripts directory on Centos  to assign multiple
 IP addresses to the same NIC on boot?

 Thanks for any and all help.

 Cheers,

 Boris.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] djbdns under CentOS7: startup and socket issues

[Boris Epstein]

On Fri, Oct 17, 2014 at 6:49 PM, James Hogarth james.hoga...@gmail.com
wrote:

 On 17 Oct 2014 23:32, Boris Epstein borepst...@gmail.com wrote:
 
  Hello all,
 
  I am trying to get djbdns ( http://en.wikipedia.org/wiki/Djbdns )
 running
  on CentOS 7. So far I have wirtten the djbdns.service and djbdns.socket
  files. The sockets (TCP and UDP 53) for some reason would not start and I
  don't know how to debug that;

 I was under the impression it used daemontools and listened directly on the
 ports rather than an inetd style behaviour of being triggered and having
 the connection handed to it like socket based behaviour would require... It
 seems unlikely you'd need a socket unit.

  the service does start but only when I start
  it manually by running
 
  systemctl start djbdns
 

 This strongly indicates you don't need the socket as socket based services
 are not stated by calling start on their service file.

 You will need to add a wantedby multi-user.target to the [install] part of
 that service file and then call systemctl enable djbdns

  So, I am a real noob when it comes to systemd, hence any advice on how to
  proceed will be much appreciated.
 

 I'd ask why you want to use djbdns rather than the DNS server provided by
 the CentOS distribution. If security is your concern then SELinux confined
 bind (in a chroot as well if you like) is supported directly by the
 distribution packages so you can be sure of updates and this list plus the
 IRC channel can support that - unlike your custom compiled djbdns.

 If you wanted to be extremely paranoid you could configure the systemd unit
 for BIND to hide all but a select number of directories too... Which is
 technically more powerful than the chroot as it makes use of kernel
 namespaces.
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos



James,

Good points.

sshd is not a telnetd-type servide yet it uses a .socket file. So I thought
djbdns should as well.

As for why DJBDNS - we have used it for a long time due to the security
advantages. And yes, BIND is now much better than it used to be and we may
switch to it at some point but for now we are still trying to get DJBDNS to
work.

I am close - when I start it manually and when I use it locally. So all I
need to do is figure out how to start it automatically as well as how to
open the necessary ports in the firewall.

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] djbdns under CentOS7: startup and socket issues

[Boris Epstein]

Hello all,

I am trying to get djbdns ( http://en.wikipedia.org/wiki/Djbdns ) running
on CentOS 7. So far I have wirtten the djbdns.service and djbdns.socket
files. The sockets (TCP and UDP 53) for some reason would not start and I
don't know how to debug that; the service does start but only when I start
it manually by running

systemctl start djbdns

So, I am a real noob when it comes to systemd, hence any advice on how to
proceed will be much appreciated.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] djbdns under CentOS7: startup and socket issues

[Boris Epstein]

On Fri, Oct 17, 2014 at 6:42 PM, Les Mikesell lesmikes...@gmail.com wrote:

 On Fri, Oct 17, 2014 at 5:31 PM, Boris Epstein borepst...@gmail.com
 wrote:
  Hello all,
 
  I am trying to get djbdns ( http://en.wikipedia.org/wiki/Djbdns )
 running
  on CentOS 7.

 There's an ndjbdns in EPEL - is that something different?

 --
   Les Mikesell
lesmikes...@gmail.com
 ___


Les,

Thanks, I don't know but I will look into it!

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 7 for i386/32-bit?

[Boris Epstein]

Hello listmates,

I can't find the 32 bit version of Centos 7. Would it be because I am not
looking in the right place or does it not exist at all?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] IP aliasing on CentOS 7

[Boris Epstein]

Hello all,

is there a good wirte-up on how edit script files in
the /etc/sysconfig/network-scripts directory on Centos  to assign multiple
IP addresses to the same NIC on boot?

Thanks for any and all help.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] patching bash 2.05b for Shellshock

[Boris Epstein]

Hello all,

Amongst a number of modern CentOS machines we have this one RHEL 3 machine
(don't ask me why:) and on it we have bash 2.05b. I was trying to compile a
version of bash for it that would be Shellshock-proofed.

To do that, I downloaded a copy of the code from the GNU along with all the
13 patches, applied the patches, compiled the code and installed the
executable. All vulnerabilities appear to be fixed with the exception
of CVE-2014-7187.

Does anybody know why this may be?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Centos box and Cisco 3750 VLAN's

[Boris Epstein]

Les and everyone,

Thanks!

I have just redone the whole setup and discovered the following: the
problem appears to have been on the Cisco side all along. The default
(natiive) VLAN on the trunk port was set to VLAN 3. Apparently, it had to
be set to VLAN 1. Once I did it the port started to work exactly as
expected, whether a VLAN is named or not!

Problem solved!

Thank you all very much again. This was an obscure one for sure.

Cheers,

Boris.


On Mon, Jun 2, 2014 at 2:11 PM, Les Mikesell lesmikes...@gmail.com wrote:

 On Mon, Jun 2, 2014 at 12:55 PM, Boris Epstein borepst...@gmail.com
 wrote:
  Hello everyone,
 
  Thanks for thoughtful and thorough advice. No luck so far, though.
 
  I have two VLAN's now - 0003 and 0004, named vlan3 and vlan4
  respectively - and still for some reason the CentOS fails to recognize
 them
  as one would expect. So I am puzzled as to what is still missing from the
  picture? Could the NIC itself (the hardware) introduce some undesired
  weirdness into the picture?

 You haven't given enough info for anyone to help.  Can you post your
 ifcfg-eth0 and ifcfg-eth0.3 files along with the error messages you
 see if there are any?

 --
Les Mikesell
 lesmikes...@gmail.com
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Centos box and Cisco 3750 VLAN's

[Boris Epstein]

Hello everyone,

Thanks for thoughtful and thorough advice. No luck so far, though.

I have two VLAN's now - 0003 and 0004, named vlan3 and vlan4
respectively - and still for some reason the CentOS fails to recognize them
as one would expect. So I am puzzled as to what is still missing from the
picture? Could the NIC itself (the hardware) introduce some undesired
weirdness into the picture?

Thanks.

Boris.



On Fri, May 30, 2014 at 4:23 PM, Blake Hudson bl...@ispn.net wrote:

 Boris, I'd suggest reviewing the guide from Redhat on configuring your
 server
 (
 https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s2-networkscripts-interfaces_802.1q-vlan-tagging.html
 )

 In essence, eth0 is a shell. eth0.x is where all the traffic happens.
 VLANs will need to be explicitly defined on both the server and the
 switch in order for traffic to pass. Again, follow the RedHat guide for
 the server configuration. Be sure to set the interface filename and the
 device name inside the file to match the VLAN ID you're using. For
 example, VLAN 1 will be /etc/sysconfig/network-scripts/ifcfg-eth0.1 and
 the first line of the file should be DEVICE=eth0.1. VLAN 2 should use
 ifcfg-eth0.2 and DEVICE=eth0.2. It's easy to forget to update the DEVICE
 field inside the file and conflict with another device on the system so
 double check all work.

 On the Cisco switch, define the VLANs:
  Switch# configure terminal
  Switch(config)# vlan 2
  Switch(config-vlan)# name vlan2
  Switch(config-vlan)# end
 ... repeat for each VLAN


 And configure the ports:
  Switch# configure terminal
  Enter configuration commands, one per line.  End with CNTL/Z.
  Switch(config)# interface gigabitethernet0/1
  Switch(config-if)# switchport mode trunk
  Switch(config-if)# switchport trunk allowed vlan 1-4
  Switch(config-if)# end
 ... repeat for other trunk ports. I'd also recommend turning off VTP and
 setting all non-trunk ports to access mode
 (
 http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750x_3560x/software/release/12-2_55_se/configuration/guide/3750xscg/swvlan.html#wp1150876
 ).

 --Blake






 Boris Epstein wrote the following on 5/30/2014 2:59 PM:
  Hello all,
 
  I have a CentOS box that has a NIC (eth0) on which I defined 4 VLAN's
  (counting the NIC itself): eth0, eth0.1, eth0.2 and eht0.3. Initially the
  Cisco switch was not partitioned into VLAN's which means that the only
 VLAN
  running on it was the default one (VLAN 1).
 
  I have then played with VLAN's a bit on the switch and at this point have
  two: VLAN 1 (which is default and can not be deleted) and VLAN 3. The
  CentOS box is plugged into a trunk port on VLAN 3 which by virtue of
 being
  a trunk should belong to all VLANs. However, this does not seem to work
 as
  expected.
 
  What I get is the following:
 
  1) eht0 does not come up at all.
 
  ifup eth0
  Device eth0 does not seem to be present, delaying initialization
 
  2) eth0.3 comes up fine.
 
  3) Other VLAN's do not come up. No error messages, just never show up.
 
  Any insight into this would be most welcome. Primarily, I fail to
  understand why all those VLAN's came up on VLAN 1 and why now even VLAN 1
  does not come up - even though the trunk port the device is plugged into
 is
  supposed to be a member of all VLAN's.
 
  Thanks in advance.
 
  Boris.
  ___
  CentOS mailing list
  CentOS@centos.org
  http://lists.centos.org/mailman/listinfo/centos

 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Centos box and Cisco 3750 VLAN's

[Boris Epstein]

Hello all,

I have a CentOS box that has a NIC (eth0) on which I defined 4 VLAN's
(counting the NIC itself): eth0, eth0.1, eth0.2 and eht0.3. Initially the
Cisco switch was not partitioned into VLAN's which means that the only VLAN
running on it was the default one (VLAN 1).

I have then played with VLAN's a bit on the switch and at this point have
two: VLAN 1 (which is default and can not be deleted) and VLAN 3. The
CentOS box is plugged into a trunk port on VLAN 3 which by virtue of being
a trunk should belong to all VLANs. However, this does not seem to work as
expected.

What I get is the following:

1) eht0 does not come up at all.

ifup eth0
Device eth0 does not seem to be present, delaying initialization

2) eth0.3 comes up fine.

3) Other VLAN's do not come up. No error messages, just never show up.

Any insight into this would be most welcome. Primarily, I fail to
understand why all those VLAN's came up on VLAN 1 and why now even VLAN 1
does not come up - even though the trunk port the device is plugged into is
supposed to be a member of all VLAN's.

Thanks in advance.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] wpa_supplicant - an utter failure, for some reason

[Boris Epstein]

Hello listmates,

I feel a little embarrassed but I can not get through this one and any help
will be much appreciated.

I have a Broadcom WiFi adapter in a 64-bit CentOS 6.5 laptop. Trying to get
it connect automatically - and it just would not - no error messages,
nothing. With the same config NetworkManager connects without a hitch,

I have to compile the wl module out of an SRPM - but after that it seemed
to work fine under the NetworkManager but not automatically, via
wpa_supplicant.

Thanks in advance for any and all advice. The WiFi security is WPA.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] VZFS issues

[Boris Epstein]

Hello listmates,

Normally whenever I needed to grab the contents of a disk/partition in its
entirety I would just use dd to pipe it wherever I wanted and that would
just work.

However, with a VZFS partition on a Parallels VM itdoes not seem to work:

root@nei [~]# dd if=/dev/vzfs of=/dev/null bs=1M count=50
dd: opening `/dev/vzfs': Permission denied
root@nei [~]#

root@nei [~]# mount
/dev/vzfs on / type reiserfs (rw,usrquota,grpquota)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /dev type tmpfs (rw,relatime)
none on /dev/pts type devpts (rw,relatime)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
none on /backup/tmpdir type tmpfs (rw,size=800M)
root@nei [~]# df
Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/vzfs 62390272  37075204  25315068  60% /
none393216 4393212   1% /dev
none819200 0819200   0% /backup/tmpdir
root@nei [~]#

Any idea why this is and how to work around it?

Any advice will be much appreciated.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] OpenVPN routing question

[Boris Epstein]

Hello all,

Let's say I have an OpenVPN (v2) server sitting on a Linux machine with the
IP address of, say, 192.168.10.1o. We are talking real address, assigned to
a NIC on the machine.

Now let us say the OpenVPN server hands out IP's in the
192.168.20.0/24range. And let us say that I want the machines able to
reach the VPN server
to be able to route to the machines available via the VPN. So, for
instance, 192.168.10.5 should be able to ping 192.168.20.6 assuming the
latter is one of the VPN clients.

So here is my question: is there a VPN setting that would facilitate that?
It seems like is is trivial enough to allow the VPN clients to route out
through the VPN server - but trying to facilitate the reverse I got stuck.

Thanks in advance for any help.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OpenVPN routing question

[Boris Epstein]

On Sun, Apr 14, 2013 at 9:06 AM, Stephen Harris li...@spuddy.org wrote:

 On Sun, Apr 14, 2013 at 09:00:16AM -0400, Boris Epstein wrote:
  Let's say I have an OpenVPN (v2) server sitting on a Linux machine with
 the
  IP address of, say, 192.168.10.1o. We are talking real address, assigned
 to
  a NIC on the machine.
 
  Now let us say the OpenVPN server hands out IP's in the
  192.168.20.0/24range. And let us say that I want the machines able to
  reach the VPN server
  to be able to route to the machines available via the VPN. So, for
  instance, 192.168.10.5 should be able to ping 192.168.20.6 assuming the
  latter is one of the VPN clients.
 
  So here is my question: is there a VPN setting that would facilitate
 that?

 In the server config file
   push route 192.168.10.0 255.255.255.0

 That will tell the openvpn client to add a route to 192.168.10.0/24 via
 the openvpn gateway.

 Machines on the LAN also need a route to 192.168.20.0/24 via the gateway;
 this is easy if your OpenVPN server is also your default gateway (eg
 router); otherwise you may need to add routes per-machine or via DHCP,
 or potentially just tell the default router about the route and let it
 send redirects to the LAN machines.

 --

 rgds
 Stephen
 ___


Stephen,

Thanks! What you are saying makes perfect sense. I have tried it.

It works for every subnet except the one the OpenVPN server sits on (
192.168.10.0/24 in our example). Yes, the VPN server has to be the default
router - or else it just does not seem to work. This additional hop just
kills everything, it seems.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] ACL/permissions question

[Boris Epstein]

Hello listmates,

If I have a regular, ACL-capable filesystem on Linux (say, ext4 or xfs) is
there a way for me to establish the following:

1) There is a directory, say, /home/joe . It is owned by user joe . No one
but joe (and root, of course) can read or write anything in this directory.

2) No one can change permissions on that directory, not even joe. In other
words, in joe all of a sudden joe decided to open his directory up to the
world (or the group he is a member of) by doing something akin to:

chmod 777 /home/joe

he would not succeed.

Thanks in advance for any help.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] load balancer recommendations

[Boris Epstein]

I have, thanks! That one works just fine.

Unfortunately, it does load balancing - and that is all. ClearOS, for
instance, does a myriad of things but the kind of load balancer I want.

And I would like to have it all in one machine. That is another challenge I
face.

Boris.


On Thu, Jan 24, 2013 at 3:03 AM, ankush grover ankushcen...@gmail.comwrote:

 You can try Zen Load Balancer

 http://www.zenloadbalancer.com/

 On Thu, Jan 24, 2013 at 1:20 PM, andreas andr...@cymail.eu wrote:

  Στις 23-01-2013 16:25, Bowie Bailey έγραψε:
   On 1/20/2013 10:12 AM, Nikolaos Milas wrote:
  
   You'll undoubtedly find more material on the iNet, but I hope the
   above
   may serve as a starting point.
  
   The iNet?  Wow, Apple's getting into everything these days...  :)
 
  A clear indication of loosing sight of core competences. Isn't it?
  ___
  CentOS mailing list
  CentOS@centos.org
  http://lists.centos.org/mailman/listinfo/centos
 
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] load balancer recommendations

[Boris Epstein]

Hello all,

Many thanks to everyone who responded with extremely helpful tips.

Reporting back that I implemented HAProxy on CentOS 6.3 and this works like
a charm - after I worked out a couple of HAProxy kinks.

Boris.


On Sat, Jan 19, 2013 at 3:35 PM, Boris Epstein borepst...@gmail.com wrote:

 Hello all,

 The question is not necessarily CentOS-specific - but there are lots of
 bright people on here, and - quite possibly - the final implementation will
 be on CentOS hence I figured I'd ask it here. Here is the situation.

 I need to configure a Linux-based network load balancer (NLB) solution.
 The idea is this. Let us say I have a public facing load balancer machine
 with an public IP of, say, 50.50.50.50. It is to receive the traffic (let's
 say, HTTP traffic) and then route it to two private HTTP servers, let's
 say, 192.168.10.10 and 192.168.10.11. It has to have persistence - i.e., be
 state- and session-aware. If for whatever reason one of the servers goes
 down the remaining pool shares all the traffic in some fashion (be it eound
 robin, saturation based, whatever).

 We have tried Vyatta ( http://vyatta.org/ ) and ZeroShell (
 http://www.zeroshell.org/ ) and both are very good but their NLB seems to
 be externally facing (i.e., you have several internet connections and are
 trying to divide your traffic between them). What we need is an internally
 facing one, if I may say so.

 Any advice on what may help us would be greatly appreciated.

 Thanks.

 Boris.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] load balancer recommendations

[Boris Epstein]

Hello all,

The question is not necessarily CentOS-specific - but there are lots of
bright people on here, and - quite possibly - the final implementation will
be on CentOS hence I figured I'd ask it here. Here is the situation.

I need to configure a Linux-based network load balancer (NLB) solution. The
idea is this. Let us say I have a public facing load balancer machine with
an public IP of, say, 50.50.50.50. It is to receive the traffic (let's say,
HTTP traffic) and then route it to two private HTTP servers, let's say,
192.168.10.10 and 192.168.10.11. It has to have persistence - i.e., be
state- and session-aware. If for whatever reason one of the servers goes
down the remaining pool shares all the traffic in some fashion (be it eound
robin, saturation based, whatever).

We have tried Vyatta ( http://vyatta.org/ ) and ZeroShell (
http://www.zeroshell.org/ ) and both are very good but their NLB seems to
be externally facing (i.e., you have several internet connections and are
trying to divide your traffic between them). What we need is an internally
facing one, if I may say so.

Any advice on what may help us would be greatly appreciated.

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] load balancer recommendations

[Boris Epstein]

Leon,

Thanks!

Looks good - though seems to be highly specific. I will check it out.

Boris.


On Sat, Jan 19, 2013 at 6:10 PM, Leon Fauster leonfaus...@googlemail.comwrote:

 Am 19.01.2013 um 21:35 schrieb Boris Epstein borepst...@gmail.com:
  Hello all,
 
  The question is not necessarily CentOS-specific - but there are lots of
  bright people on here, and - quite possibly - the final implementation
 will
  be on CentOS hence I figured I'd ask it here. Here is the situation.
 
  I need to configure a Linux-based network load balancer (NLB) solution.
 The
  idea is this. Let us say I have a public facing load balancer machine
 with
  an public IP of, say, 50.50.50.50. It is to receive the traffic (let's
 say,
  HTTP traffic) and then route it to two private HTTP servers, let's say,
  192.168.10.10 and 192.168.10.11. It has to have persistence - i.e., be
  state- and session-aware. If for whatever reason one of the servers goes
  down the remaining pool shares all the traffic in some fashion (be it
 eound
  robin, saturation based, whatever).
 
  We have tried Vyatta ( http://vyatta.org/ ) and ZeroShell (
  http://www.zeroshell.org/ ) and both are very good but their NLB seems
 to
  be externally facing (i.e., you have several internet connections and are
  trying to divide your traffic between them). What we need is an
 internally
  facing one, if I may say so.
 
  Any advice on what may help us would be greatly appreciated.



 Did you check haproxy - http://haproxy.1wt.eu.

 Application session should be shared via distributed
 key-value store (e.g. redis). Speak another instance
 to manage.

 --
 LF



 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] load balancer recommendations

[Boris Epstein]

Joseph,

Thanks!

Did you mean this:

https://www.barracudanetworks.com/products/loadbalancer

But this looks like an integrated solution, hardware and software. I am
just looking for the software part.

Boris.


On Sat, Jan 19, 2013 at 7:06 PM, Joseph Spenner joseph85...@yahoo.comwrote:

 Am 19.01.2013 um 21:35 schrieb Boris Epstein borepst...@gmail.com:

   Hello all,
  
   The question is not necessarily CentOS-specific - but there are lots of
   bright people on here, and - quite possibly - the final implementation
  will
   be on CentOS hence I figured I'd ask it here. Here is the situation.
  
   I need to configure a Linux-based network load balancer (NLB) solution.
  The
   idea is this. Let us say I have a public facing load balancer machine
  with
   an public IP of, say, 50.50.50.50. It is to receive the traffic (let's
  say,
   HTTP traffic) and then route it to two private HTTP servers, let's say,
   192.168.10.10 and 192.168.10.11. It has to have persistence - i.e., be
   state- and session-aware. If for whatever reason one of the servers
 goes
   down the remaining pool shares all the traffic in some fashion (be it
  eound
   robin, saturation based, whatever).
  
   We have tried Vyatta ( http://vyatta.org/ ) and ZeroShell (
   http://www.zeroshell.org/ ) and both are very good but their NLB seems
  to
   be externally facing (i.e., you have several internet connections and
 are
   trying to divide your traffic between them). What we need is an
  internally
   facing one, if I may say so.
  
   Any advice on what may help us would be greatly appreciated.

 I've had pretty good luck with Barracuda load balancers..  You can
 configure them to keep a user session on a single server, which is often
 desired, and spread new connections to other servers as they arrive.
 The only problem I had with them, ironically, was they would crash if I
 purchased their Live Updates feature.  It's some sort of auto updating
 black-list service you can buy which helps protect the device and your
 resources.  But after I disabled that, the device has been rock solid.
 Been working great since about 2006.




  If life gives you lemons, keep them-- because hey.. free lemons.
 ~heart~ Sticker  fixer:
 http://microflush.org/stuff/stickers/heartFix.html
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] load balancer recommendations

[Boris Epstein]

Absolutely. The solution seems really robust and the price is not bad.

In my case, however, this is not the answer as I need a solution that can
be implemented in a whole variety of networks, including virtual ones.

Thanks anyways.

Boris.


On Sat, Jan 19, 2013 at 7:18 PM, Joseph Spenner joseph85...@yahoo.comwrote:

 From: Boris Epstein borepst...@gmail.com

 To: CentOS mailing list centos@centos.org
 Sent: Saturday, January 19, 2013 5:10 PM
 Subject: Re: [CentOS] load balancer recommendations

 Joseph,

 Thanks!

 Did you mean this:

 https://www.barracudanetworks.com/products/loadbalancer

 But this looks like an integrated solution, hardware and software. I am
 just looking for the software part.

 Boris.

 On Sat, Jan 19, 2013 at 7:06 PM, Joseph Spenner joseph85...@yahoo.com
 wrote:

 
  I've had pretty good luck with Barracuda load balancers..  You can
  configure them to keep a user session on a single server, which is often
  desired, and spread new connections to other servers as they arrive.
  The only problem I had with them, ironically, was they would crash if I
  purchased their Live Updates feature.  It's some sort of auto updating
  black-list service you can buy which helps protect the device and your
  resources.  But after I disabled that, the device has been rock solid.
  Been working great since about 2006.
 

 Yes.  It might be worth just getting the whole canned solution, though.
 It is Linux based.
 At the time, the thing was about $1800, which isn't really that bad, and
 it just works.  There's a web interface to configure it, and it's
 relatively intuitive.



  If life gives you lemons, keep them-- because hey.. free lemons.
 ~heart~ Sticker  fixer:
 http://microflush.org/stuff/stickers/heartFix.html
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] two IP addresses on the same NIC: one via DHCP, one fixed

[Boris Epstein]

Hello listmates,

If I have a NIC on my CentOS 6.2 machine two which I want to assign to IP
addresses: one acquired via DHCP, the other one fixed - is there a way to
do that? How do I do that?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] two IP addresses on the same NIC: one via DHCP, one fixed

[Boris Epstein]

On Mon, Oct 1, 2012 at 5:46 PM, Leon Fauster leonfaus...@googlemail.comwrote:

 Am 01.10.2012 um 22:53 schrieb Boris Epstein:
  Hello listmates,
 
  If I have a NIC on my CentOS 6.2 machine two which I want to assign to IP
  addresses: one acquired via DHCP, the other one fixed - is there a way to
  do that? How do I do that?


 aliases are used to bind a second ip to the interface but this only
 works with static ips.

 --
 LF




Yes, thank you very much.

It's a non-issue - I just got the alias syntax wrong.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] load balancer recommendation

[Boris Epstein]

Hello all,

If I were looking for a load balancer to run on a Linux - specifically,
CentOS - machine - what would you recommend?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] netcat issue: no UDP transmission

[Boris Epstein]

Hello listamtes,

Here's is a curious issue: netcat (nc) seems to not do UDP for me, even
though TCP works flawlessly. Not even on the local host.

Here's the server session I am running:

cat test.dd | nc -l -u -n -k -v 2456

(test.dd is just a large file with random data)

Here's the client:

nc -v -u 127.0.0.1 2456 | dd of=/dev/null
^C0+0 records in
0+0 records out
0 bytes (0 B) copied, 219.944 s, 0.0 kB/s

Here's what netstat reports:

netstat -a -n | grep 2456
udp0  0 0.0.0.0:24560.0.0.0:*

udp0  0 127.0.0.1:52394 127.0.0.1:2456
 ESTABLISHED
unix  3  [ ] STREAM CONNECTED 12456

So the connection is established - but no data appears to be getting
transferred.

This behaviour seems to be the same on CentOS 6 and LinuxMint. Any idea
what may be going on?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] default gateway outside of the LAN

[Boris Epstein]

Hello all,

We have a somewhat unique setup whereby our default router is outside of
the local network.

Let us say our network is 192.168.10.0/255.255.255.0

So we have a route-eth0 file that looks something like this:

10.1.1.1 via 192.168.10.1 dev eth0
default 10.1.1.1 dev eth0

The last definition would simply not take - but it has to for the setup to
work. And no, 192.168.10.1 does not operate as a full-fledge router due to
our setup.

When we attempt to add it manually we get the following error:

RTNETLINK answers: No such process

When we use ifup we get the following:

Error: either to is a duplicate, or 10.1.1.1 is a garbage.

A little discussion of this can be found here:

http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s1-networkscripts-static-routes.html

and here:

http://www.linuxquestions.org/questions/linux-networking-3/etc-init-d-networking-restart-errors-637610/

It does not help us, however. Any tips much appreciated.

Cheers,

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] missing V4L or related dependencies

[Boris Epstein]

Hello again,

Looks like the functions I need - at least some of them - are defined in

videobuf-vmalloc.h

I still have no idea where to find them - i.e., what to include/install to
make them resolve.

Boris.

On Mon, Jul 23, 2012 at 5:48 PM, Boris Epstein borepst...@gmail.com wrote:

 Hello all,

 I am trying to install Epiphan's ( http://www.epiphan.com/ ) VGA2USB
 device on a Centos 6 machine and when I am trying to compile and install
 the driver for it I get the following errors:

 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_streamoff
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_poll_stream
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol video_ioctl2
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_reqbufs
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_dqbuf
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_to_vmalloc
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_vmalloc_free
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol video_devdata
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_stop
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_read_stream
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_querybuf
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol video_unregister_device
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_qbuf
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol video_register_device
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_iolock
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_streamon
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_queue_vmalloc_init
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_mmap_mapper
 WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
 unknown symbol videobuf_mmap_free

 Does anybody happen to know which library I need to install to get these
 functions?

 Thanks.

 Boris.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] missing V4L or related dependencies

[Boris Epstein]

On Tue, Jul 24, 2012 at 2:41 PM, m.r...@5-cent.us wrote:

 Boris Epstein wrote:
  Hello again,
 
  Looks like the functions I need - at least some of them - are defined in
 
  videobuf-vmalloc.h
 
  I still have no idea where to find them - i.e., what to include/install
 to
  make them resolve.

 Ah, a locate found it. It's in kernel-devel.

   mark



OK... thanks Mark!

Then how come I fail to link to it?

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] missing V4L or related dependencies

[Boris Epstein]

On Tue, Jul 24, 2012 at 2:48 PM, m.r...@5-cent.us wrote:

 Boris Epstein wrote:
  On Tue, Jul 24, 2012 at 2:41 PM, m.r...@5-cent.us wrote:
  Boris Epstein wrote:
   Hello again,
  
   Looks like the functions I need - at least some of them - are defined
   in videobuf-vmalloc.h
  
   I still have no idea where to find them - i.e., what to
   include/install to make them resolve.
 
  Ah, a locate found it. It's in kernel-devel.
 
  OK... thanks Mark!
 
  Then how come I fail to link to it?

 Wait - this is in something already compiled, or are you building it? If
 the former, then for some reason, it may not be in your link path, or you
 might need to add it to LD_LIBRARY_PATH. If the former, I dunno why it
 wouldn't have the path right. You're not building a 32-bit on a 64 bit, or
 vice versa, are you?

mark

 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos


Mark,

I was trying to compile the software on a 64-bit machine. kernel-devel was
installed. After I ran a

yum update

and rebooted the system the compilation worked like a charm.

This must have been some ldconfig issue or some such.

Thanks for your help.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] missing V4L or related dependencies

[Boris Epstein]

Hello all,

I am trying to install Epiphan's ( http://www.epiphan.com/ ) VGA2USB device
on a Centos 6 machine and when I am trying to compile and install the
driver for it I get the following errors:

WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_streamoff
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_poll_stream
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol video_ioctl2
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_reqbufs
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_dqbuf
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_to_vmalloc
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_vmalloc_free
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol video_devdata
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_stop
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_read_stream
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_querybuf
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol video_unregister_device
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_qbuf
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol video_register_device
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_iolock
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_streamon
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_queue_vmalloc_init
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_mmap_mapper
WARNING: /lib/modules/2.6.32-279.2.1.el6.x86_64/extra/vga2usb.ko needs
unknown symbol videobuf_mmap_free

Does anybody happen to know which library I need to install to get these
functions?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] FreeIPA on Centos 6

[Boris Epstein]

On Wed, Jun 27, 2012 at 2:39 AM, James Hogarth james.hoga...@gmail.comwrote:

  Named segfaulted here and there, and when the master instance failed,
  takeover didn't work for whatever reason.
 

 I have four IPAs replicating together across two DCs with full DNS and CA
 integration plus using it for sudo management as well fully stable.

 Have never seen the behaviour you describe and there is no 'master' to take
 over from since it is multi master so no take over even exists much
 less is required
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos


Thanks. What's DC in this context?

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] FreeIPA on Centos 6

[Boris Epstein]

Hello all,

Is anybody using http://freeipa.org on a CentOS 6 server? Is it working
well?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] XFS-in-a-file

[Boris Epstein]

Hello listmates,

Has anybody attempted to run an XFS in a file mounted via -o loop? The file
size is about 20 TB and it resides in a larger XFS filesystem residing on a
disk. That filesystem's size is about 25 TB. What sort of degradation
should one expect under that sort of scenario?

The reason I am asking is that I am trying to run a MooseFS chunkserver in
that filesystem-in-a-file and looks like I am getting some pretty bad
delays.

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] unfsd scalability issues

[Boris Epstein]

On Thu, Jun 14, 2012 at 1:15 PM, Boris Epstein borepst...@gmail.com wrote:



 On Wed, Jun 13, 2012 at 10:11 AM, m.r...@5-cent.us wrote:

 Boris Epstein wrote:
  On Sat, Jun 2, 2012 at 2:50 PM, John R. Dennison j...@gerdesas.com
 wrote:
  On Sat, Jun 02, 2012 at 10:59:13AM -0400, Boris Epstein wrote:
 snip
  To be specific, I use UNFSD to export a MooseFS file system. MooseFS, by
  the way, is userland-process based too.
 
  Be that as it may, I've seen situations where a comparably configured
  MooseFS client get to read at, say, 40 MB/s - which is fine - but the
  UNFSD at the same time reads at 40K/s(!) Why would that be? I mean, some
  degradation I can dig but 3 orders of magnitude? What is with this? Am I
  doing something wrong?
 snip
 I wonder... what's the architecture of what you're getting these results?
 I tried opening a bug with upstream over NFS4 and 6.x, and no one ever
 looked at it, and they closed it.

 100% repeatably: unpack a package locally, seconds.
 unpack it from an NFS mount onto a local drive, about 1
 min.
 unpack it from an NFS mount onto an NFS mount, even when
the target is exported FROM THE SAME MACHINE* that the
process is running on: 6.5 - 7 MINUTES.

 * That is,
 [server 1] [server 2]
/export/thatdir --NFS--/target/dir
/s2/source
/source/dir --NFS--/s2/source
 and cd [server 2]:/target/dir and unpack from /s2/source

 I suppose I'll try logging into upstream's bugzilla using our official
 licensed id; maybe then they'll assign someone to look at it

mark



 Mark,

 Thanks, my architecture is extremely similar to yours, except that in my
 case the second layer, if I may say so, is MooseFS (
 http://www.moosefs.org/ ), not NFS. MooseFS itself is blazing, by the way.

 So the diagram in my case would look something like this:

/export/thatdir --NFS--/target/dir
/s2/source
/source/dir -- MooseFS mount (mfsmount)
 --/s2/source

 The discrepancy in the resultant performance is comparable.

 Thanks.

 Boris.


I may have discovered a fix. Still don't know why it is a fix - but for
what it's worth...

OK, if you put your UNFSD daemon on a completely different physical machine
- i.e., with no MooseFS component running on it - it seems to work just
fine. For a single client I got a performance of about 70 MB/s over 1
Gbit/s network. When multiple (up to 5) clients) do their reads the
performance seems to degrade roughly proportionally.

And this is strange. I've got MooseFS currently confined to just one
machine (8 cores, 48 GB RAM): master server, meta server, chunk server, the
whole thing. And that works fine. Add UNFSD - and it still works, and the
load is still low (under 1) - and yet the UNFSD's performance goes down the
drain. Why? I have no idea.

By the way, the autonomous UNFSD server is far from a powerful piece of
software - all it is is a P5-class 2-core machine with 2 GB of RAM. So go
figure...

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] unfsd scalability issues

[Boris Epstein]

On Wed, Jun 13, 2012 at 10:11 AM, m.r...@5-cent.us wrote:

 Boris Epstein wrote:
  On Sat, Jun 2, 2012 at 2:50 PM, John R. Dennison j...@gerdesas.com
 wrote:
  On Sat, Jun 02, 2012 at 10:59:13AM -0400, Boris Epstein wrote:
 snip
  To be specific, I use UNFSD to export a MooseFS file system. MooseFS, by
  the way, is userland-process based too.
 
  Be that as it may, I've seen situations where a comparably configured
  MooseFS client get to read at, say, 40 MB/s - which is fine - but the
  UNFSD at the same time reads at 40K/s(!) Why would that be? I mean, some
  degradation I can dig but 3 orders of magnitude? What is with this? Am I
  doing something wrong?
 snip
 I wonder... what's the architecture of what you're getting these results?
 I tried opening a bug with upstream over NFS4 and 6.x, and no one ever
 looked at it, and they closed it.

 100% repeatably: unpack a package locally, seconds.
 unpack it from an NFS mount onto a local drive, about 1
 min.
 unpack it from an NFS mount onto an NFS mount, even when
the target is exported FROM THE SAME MACHINE* that the
process is running on: 6.5 - 7 MINUTES.

 * That is,
 [server 1] [server 2]
/export/thatdir --NFS--/target/dir
/s2/source
/source/dir --NFS--/s2/source
 and cd [server 2]:/target/dir and unpack from /s2/source

 I suppose I'll try logging into upstream's bugzilla using our official
 licensed id; maybe then they'll assign someone to look at it

mark



Mark,

Thanks, my architecture is extremely similar to yours, except that in my
case the second layer, if I may say so, is MooseFS (
http://www.moosefs.org/ ), not NFS. MooseFS itself is blazing, by the way.

So the diagram in my case would look something like this:

   /export/thatdir --NFS--/target/dir
   /s2/source
   /source/dir -- MooseFS mount (mfsmount)
--/s2/source

The discrepancy in the resultant performance is comparable.

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] unfsd scalability issues

[Boris Epstein]

On Sat, Jun 2, 2012 at 2:50 PM, John R. Dennison j...@gerdesas.com wrote:

 On Sat, Jun 02, 2012 at 10:59:13AM -0400, Boris Epstein wrote:
 
  A process implemented in the userland may not be as efficient as one
  implemented as part of the kernel - but that doesn't mean it can't scale
  well, does it?

 Depends on ones definition of scale I suppose.  I consider efficiency
 and performance one factor of scaling.  To be completely honest about
 this I must admit that I've not spent a lot of time benchmarking any
 user space implementation in a large deployment but I wouldn't expect
 performance to ramp up based on scale.

 I've always had a strong aversion to file systems implemented in
 user space versus kernel space as I've (personally) never found such an
 implementation that had what I considered good performance.

 My needs, however, are not yours.  If your requirements give you leeway
 for higher latency and slower overall performance perhaps a userland
 file system will work perfectly fine for you.  As with all else in the
 IT sector use what works best for you :)





John
 --
 Human beings hardly ever learn from the experience of others.  They learn;
 when they do, which isn't often, on their own, the hard way.

 -- Robert Heinlein (1907-1988), American science fiction writer, Time
   Enough for Love (1973)




John,

To be specific, I use UNFSD to export a MooseFS file system. MooseFS, by
the way, is userland-process based too.

Be that as it may, I've seen situations where a comparably configured
MooseFS client get to read at, say, 40 MB/s - which is fine - but the UNFSD
at the same time reads at 40K/s(!) Why would that be? I mean, some
degradation I can dig but 3 orders of magnitude? What is with this? Am I
doing something wrong?

I can't believe it works the same way for everybody - who would use it if
it did?

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] working dhcpd.conf with routes

[Boris Epstein]

Hello listmates,

I am running DHCPD for IPv4 on a Centos 5 machine. I am wondering if anyone
has got a functional dhcpd.conf configuration serving static routes to
Linux, Mac OS X and Windows clients.

I tried a couple of variations of static-routes options - but have yet to
create something that would work.

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] working dhcpd.conf with routes

[Boris Epstein]

On Mon, Jun 11, 2012 at 5:51 PM, Rob Kampen rkam...@kampensonline.comwrote:

 On 06/12/2012 09:14 AM, Boris Epstein wrote:

 Hello listmates,

 I am running DHCPD for IPv4 on a Centos 5 machine. I am wondering if
 anyone
 has got a functional dhcpd.conf configuration serving static routes to
 Linux, Mac OS X and Windows clients.

 I tried a couple of variations of static-routes options - but have yet to
 create something that would work.

 Use this:
 ddns-domainname mydomainname.com;
 ddns-update-style interim;
 ddns-rev-domainname in-addr.arpa;
 ddns-updates on;
 ignore client-updates;

 key DHCP_UPDATER {
algorithm hmac-md5;
secret ;
 };

 zone mydomainname.com. {
primary 192.168.1.10;
key DHCP_UPDATER;
 }

 zone 1.168.192.in-addr.arpa. {
primary 192.168.1.10;
key DHCP_UPDATER;
 }

 subnet 192.168.1.0 netmask 255.255.255.0 {
authoritative;
# --- default gateway
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option nis-domain mydomainname.com;
option domain-name mydomainname.com;
option domain-name-servers 192.168.1.1 , 192.168.1.2 ;
option time-offset -18000;
option ntp-servers 192.168.1.2;
option netbios-name-servers 192.168.1.10;
range dynamic-bootp 192.168.1.64 192.168.1.127;
default-lease-time 21600;
max-lease-time 43200;
 }
# we want the nameserver to appear at a fixed address
host iPhone {
next-server iPhone.mydomainname.com;
hardware ethernet 00:24:36:49:42:81;
fixed-address 192.168.1.192;
}
host Australia {
next-server australia.mydomainname.com;
hardware ethernet 00:24:8c:81:0c:15;
fixed-address 192.168.1.202;
}
host D610 {
next-server D610.mydomainname.com;
hardware ethernet 00:90:4b:c7:54:fb;
fixed-address 192.168.1.201;
}

 Hope this helps




Rob,

Thanks, looks good. But what part of it deals with static routes for
particular networks? All I see is one default gateway:

option routers 192.168.1.1;

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] working dhcpd.conf with routes

[Boris Epstein]

On Mon, Jun 11, 2012 at 6:32 PM, Rob Kampen rkam...@reaching-clients.comwrote:

 On 06/12/2012 10:05 AM, Boris Epstein wrote:

 On Mon, Jun 11, 2012 at 5:51 PM, Rob 
 Kampenrkampen@kampensonline.**comrkam...@kampensonline.com
 wrote:

  On 06/12/2012 09:14 AM, Boris Epstein wrote:

  Hello listmates,

 I am running DHCPD for IPv4 on a Centos 5 machine. I am wondering if
 anyone
 has got a functional dhcpd.conf configuration serving static routes to
 Linux, Mac OS X and Windows clients.

 I tried a couple of variations of static-routes options - but have yet
 to
 create something that would work.

  Use this:
 ddns-domainname mydomainname.com;
 ddns-update-style interim;
 ddns-rev-domainname in-addr.arpa;
 ddns-updates on;
 ignore client-updates;

 key DHCP_UPDATER {
algorithm hmac-md5;
secret ;
 };

 zone mydomainname.com. {
primary 192.168.1.10;
key DHCP_UPDATER;
 }

 zone 1.168.192.in-addr.arpa. {
primary 192.168.1.10;
key DHCP_UPDATER;
 }

 subnet 192.168.1.0 netmask 255.255.255.0 {
authoritative;
# --- default gateway
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option nis-domain mydomainname.com;
option domain-name mydomainname.com;
option domain-name-servers 192.168.1.1 , 192.168.1.2 ;
option time-offset -18000;
option ntp-servers 192.168.1.2;
option netbios-name-servers 192.168.1.10;
range dynamic-bootp 192.168.1.64 192.168.1.127;
default-lease-time 21600;
max-lease-time 43200;
 }
# we want the nameserver to appear at a fixed address
host iPhone {
next-server iPhone.mydomainname.com;
hardware ethernet 00:24:36:49:42:81;
fixed-address 192.168.1.192;
}
host Australia {
next-server australia.mydomainname.com;
hardware ethernet 00:24:8c:81:0c:15;
fixed-address 192.168.1.202;
}
host D610 {
next-server D610.mydomainname.com;
hardware ethernet 00:90:4b:c7:54:fb;
fixed-address 192.168.1.201;
}

 Hope this helps



  Rob,

 Thanks, looks good. But what part of it deals with static routes for
 particular networks? All I see is one default gateway:

 option routers 192.168.1.1;

 The subnet ip4address/mask {...} defines the information that is
 available to the clients for that subnet.
 The host clientname { .} defines the static ip address and name to be
 used for a given ethernet.



Rob,

You may be confusing two different things: static IP addresses for
individual hosts and static routes to route IP traffic to certain subnets.

Thanks anyways.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] unfsd scalability issues

[Boris Epstein]

On Sat, Jun 2, 2012 at 6:16 AM, Johnny Hughes joh...@centos.org wrote:

 On 06/01/2012 10:26 PM, Boris Epstein wrote:
  On Fri, Jun 1, 2012 at 6:36 PM, John R Pierce pie...@hogranch.com
 wrote:
 
  On 06/01/12 2:27 PM, Boris Epstein wrote:
  I believe that unfsd (http://unfs3.sourceforge.net/  ) now does have
  multi-threaded capability and as such should be fairly well scalable. I
  am
  using it on CentOS 6.2 and it seems to become all but unusable when
 more
  then 3-4 users connect to it. Is that normal? What sort of experience
  have
  other people had?
  yeesh, wtf ?
 
  latest version: 0.9.222009-01-05
 
  WHY?!??!   what problem is this supposed to solve over the built in
  native Linux NFS, which supports a lot more than just NFSv3?
 
 
  maybe in 2003, when Linux NFS was sketchy, this made sense.
 
 
  --
  john r pierceN 37, W 122
  santa cruz ca mid-left coast
 
 
 
  John,
  The native NFS only supports the local file system (on the local disk).
  What we have here is an NFS gateway to a distributed file system, in our
  case MooseFS ( http://www.moosefs.org/ ).
 

 You might take a look at GlusterFS for your distributed file system if
 most of your nodes are on the same 100mbit or 1Gbit network.  GlusterFS
 is the new big thing that Red Hat is going to support and we use it on
 the CentOS infrastructure and like it quite well.  It is also very easy
 to maintain and you can mount it via the glusterfs client or via NFS.
 It does not work real well across a slower internet like in multiple
 datacenters, but if your machines are all on a fast network with each
 other, I highly recommend it.


 John,

I agree with you that GlusterFS is not bad - though neither is MooseFs,
based on all accounts, and MooseFS is very simple and lightweight, which
was why we chose it. At any rate, at this point this is what we are using.
All we need is an NFS gateway that would scale to 10-20 sessions without
losing too much performance.

And yes, it could be that it is my MooseFS that is underperforming - I am
studying that possibility too.

Thanks!

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] unfsd scalability issues

[Boris Epstein]

On Sat, Jun 2, 2012 at 8:50 AM, Dennis Jacobfeuerborn denni...@conversis.de
 wrote:

 On 06/02/2012 02:16 PM, Boris Epstein wrote:
  On Sat, Jun 2, 2012 at 6:16 AM, Johnny Hughes joh...@centos.org wrote:
 
  On 06/01/2012 10:26 PM, Boris Epstein wrote:
  On Fri, Jun 1, 2012 at 6:36 PM, John R Pierce pie...@hogranch.com
  wrote:
 
  On 06/01/12 2:27 PM, Boris Epstein wrote:
  I believe that unfsd (http://unfs3.sourceforge.net/  ) now does have
  multi-threaded capability and as such should be fairly well
 scalable. I
  am
  using it on CentOS 6.2 and it seems to become all but unusable when
  more
  then 3-4 users connect to it. Is that normal? What sort of experience
  have
  other people had?
  yeesh, wtf ?
 
  latest version: 0.9.222009-01-05
 
  WHY?!??!   what problem is this supposed to solve over the built in
  native Linux NFS, which supports a lot more than just NFSv3?
 
 
  maybe in 2003, when Linux NFS was sketchy, this made sense.
 
 
  --
  john r pierceN 37, W 122
  santa cruz ca mid-left coast
 
 
 
  John,
  The native NFS only supports the local file system (on the local disk).
  What we have here is an NFS gateway to a distributed file system, in
 our
  case MooseFS ( http://www.moosefs.org/ ).
 
 
  You might take a look at GlusterFS for your distributed file system if
  most of your nodes are on the same 100mbit or 1Gbit network.  GlusterFS
  is the new big thing that Red Hat is going to support and we use it on
  the CentOS infrastructure and like it quite well.  It is also very easy
  to maintain and you can mount it via the glusterfs client or via NFS.
  It does not work real well across a slower internet like in multiple
  datacenters, but if your machines are all on a fast network with each
  other, I highly recommend it.
 
 
  John,
 
  I agree with you that GlusterFS is not bad - though neither is MooseFs,
  based on all accounts, and MooseFS is very simple and lightweight, which
  was why we chose it. At any rate, at this point this is what we are
 using.
  All we need is an NFS gateway that would scale to 10-20 sessions without
  losing too much performance.
 
  And yes, it could be that it is my MooseFS that is underperforming - I am
  studying that possibility too.

 MooseFS is really only designed to host large files and to be useful if you
 care about throughput but not latency. GlusterFS is going to perform much
 better as a regular filesystem due to its consistent hashing approach and
 is just as simple and lightweigt as MooseFS.

 But why can't you mount MooseFS locally and then export it using the
 regular nfs implementation?

 Regards,
  Dennis

 PS: You might also take a look at Ceph at ceph.com and Sheepdog at
 www.osrg.net/sheepdog. Both two very interesting contenders. You can find
 some interesting benchmarks for a 1000 node Sheepdog cluster here:
 http://sheepdog.taobao.org/people/zituan/sheepdog1k.html

 Regards,
  Dennis
 ___



Dennis,

Thanks for a thoughtful reply.

I believe the regular NFS does not allow you to export non-local
directories. That was so a few years ago; I didn't even check for myself
this time around as people are saying this is still the case. Perhaps I
should check.

When you are saying that MooseFS is high latency - what sort of latency
should I expect when accessing a file, though? There's a whole community of
happy MooseFS users out there; I am not sure they'd be so happy if you had
to wait for 30 seconds to just start reading a file. We could tolerate some
latency here, by the way.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] unfsd scalability issues

[Boris Epstein]

On Sat, Jun 2, 2012 at 8:50 AM, Dennis Jacobfeuerborn denni...@conversis.de
 wrote:

 On 06/02/2012 02:16 PM, Boris Epstein wrote:
  On Sat, Jun 2, 2012 at 6:16 AM, Johnny Hughes joh...@centos.org wrote:
 
  On 06/01/2012 10:26 PM, Boris Epstein wrote:
  On Fri, Jun 1, 2012 at 6:36 PM, John R Pierce pie...@hogranch.com
  wrote:
 
  On 06/01/12 2:27 PM, Boris Epstein wrote:
  I believe that unfsd (http://unfs3.sourceforge.net/  ) now does have
  multi-threaded capability and as such should be fairly well
 scalable. I
  am
  using it on CentOS 6.2 and it seems to become all but unusable when
  more
  then 3-4 users connect to it. Is that normal? What sort of experience
  have
  other people had?
  yeesh, wtf ?
 
  latest version: 0.9.222009-01-05
 
  WHY?!??!   what problem is this supposed to solve over the built in
  native Linux NFS, which supports a lot more than just NFSv3?
 
 
  maybe in 2003, when Linux NFS was sketchy, this made sense.
 
 
  --
  john r pierceN 37, W 122
  santa cruz ca mid-left coast
 
 
 
  John,
  The native NFS only supports the local file system (on the local disk).
  What we have here is an NFS gateway to a distributed file system, in
 our
  case MooseFS ( http://www.moosefs.org/ ).
 
 
  You might take a look at GlusterFS for your distributed file system if
  most of your nodes are on the same 100mbit or 1Gbit network.  GlusterFS
  is the new big thing that Red Hat is going to support and we use it on
  the CentOS infrastructure and like it quite well.  It is also very easy
  to maintain and you can mount it via the glusterfs client or via NFS.
  It does not work real well across a slower internet like in multiple
  datacenters, but if your machines are all on a fast network with each
  other, I highly recommend it.
 
 
  John,
 
  I agree with you that GlusterFS is not bad - though neither is MooseFs,
  based on all accounts, and MooseFS is very simple and lightweight, which
  was why we chose it. At any rate, at this point this is what we are
 using.
  All we need is an NFS gateway that would scale to 10-20 sessions without
  losing too much performance.
 
  And yes, it could be that it is my MooseFS that is underperforming - I am
  studying that possibility too.

 MooseFS is really only designed to host large files and to be useful if you
 care about throughput but not latency. GlusterFS is going to perform much
 better as a regular filesystem due to its consistent hashing approach and
 is just as simple and lightweigt as MooseFS.

 But why can't you mount MooseFS locally and then export it using the
 regular nfs implementation?

 Regards,
  Dennis


Dennis,

I just tried exporting a MooseFS partition using regular NFS and got the
following:

Jun  2 10:32:24 fs1 rpc.mountd[2500]: Cannot export /mfs/mfs1, possibly
unsupported filesystem or fsid= required

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] unfsd scalability issues

[Boris Epstein]

On Fri, Jun 1, 2012 at 6:46 PM, John R. Dennison j...@gerdesas.com wrote:

 On Fri, Jun 01, 2012 at 03:36:09PM -0700, John R Pierce wrote:
 
  maybe in 2003, when Linux NFS was sketchy, this made sense.

 Unlikely back then, either.  It's a userland implementation, subject to
 all the same scheduling issues as any other userland app; filesystems
 should not be implemented in userland for efficiency reasons.





John


John,

A process implemented in the userland may not be as efficient as one
implemented as part of the kernel - but that doesn't mean it can't scale
well, does it?

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] unfsd scalability issues

[Boris Epstein]

 A process implemented in the userland may not be as efficient as one
  implemented as part of the kernel - but that doesn't mean it can't scale
  well, does it?

 Anything that needs atomic operations is difficult to scale.  Throw in
 distributed components and an extra user/kernel layer and there are
 lots of ways to go wrong.

 --
   Les Mikesell
 lesmikes...@gmail.com


Les, what doesn't need atomic operations? And how doing things in kernel
makes your program more scalable - it is the algorithm that matters, not
the execution space, IMO.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] unfsd scalability issues

[Boris Epstein]

Hello there,

I believe that unfsd ( http://unfs3.sourceforge.net/ ) now does have
multi-threaded capability and as such should be fairly well scalable. I am
using it on CentOS 6.2 and it seems to become all but unusable when more
then 3-4 users connect to it. Is that normal? What sort of experience have
other people had?

Is there a way to parametrically tune it, by the way?

Thanks.

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] unfsd scalability issues

[Boris Epstein]

On Fri, Jun 1, 2012 at 6:36 PM, John R Pierce pie...@hogranch.com wrote:

 On 06/01/12 2:27 PM, Boris Epstein wrote:
  I believe that unfsd (http://unfs3.sourceforge.net/  ) now does have
  multi-threaded capability and as such should be fairly well scalable. I
 am
  using it on CentOS 6.2 and it seems to become all but unusable when more
  then 3-4 users connect to it. Is that normal? What sort of experience
 have
  other people had?

 yeesh, wtf ?

 latest version: 0.9.222009-01-05

 WHY?!??!   what problem is this supposed to solve over the built in
 native Linux NFS, which supports a lot more than just NFSv3?


 maybe in 2003, when Linux NFS was sketchy, this made sense.


 --
 john r pierceN 37, W 122
 santa cruz ca mid-left coast



 John,

The native NFS only supports the local file system (on the local disk).
What we have here is an NFS gateway to a distributed file system, in our
case MooseFS ( http://www.moosefs.org/ ).

Boris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos