Re: [CentOS] ipset not actually blocking

2014-12-10 Thread Rob Townley 
Appears the iptables update 1.4.7-14 which came with CentOS6 r6 is the most
likely culprit.

The solution for now is:
delete ',dst' from the iptables INPUT chain
delete 'src,' from the iptables OUTPUT chain.




On Mon, Dec 8, 2014 at 5:39 PM, Rob Townley  wrote:

> i created an ipset and added 8.8.8.8 to it and used the same iptables
> working all summer long  but
> ​i can still ping 8.8.8.8 and do nslookup queries against it.   ipset or
> iptables is broken.
>   Anybody else rebooted since  ipset-6.11-3.el6.i686 was installed and
> actually tested that IP addresses that are supposed to be blacklisted are
> actually blocked?
> ​
>
> Filed CentOS bug report 7977 
> this morning.  ipset was working great most of the year until ipset 6.11.-3
> CentOS bug 7977​ 
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] ipset not actually blocking

2014-12-10 Thread Rob Townley 
Incidentally, a different OS has a newer version of  iptables
1.4.18-1.1ubuntu1, but still works the old way where SRC still matches
SRC,DST.

On Wed, Dec 10, 2014 at 2:03 AM, Rob Townley  wrote:

> Appears the iptables update 1.4.7-14 which came with CentOS6 r6 is the
> most likely culprit.
>
> The solution for now is:
> delete ',dst' from the iptables INPUT chain
> delete 'src,' from the iptables OUTPUT chain.
>
>
>
>
> On Mon, Dec 8, 2014 at 5:39 PM, Rob Townley  wrote:
>
>> i created an ipset and added 8.8.8.8 to it and used the same iptables
>> working all summer long  but
>> ​i can still ping 8.8.8.8 and do nslookup queries against it.   ipset or
>> iptables is broken.
>>   Anybody else rebooted since  ipset-6.11-3.el6.i686 was installed and
>> actually tested that IP addresses that are supposed to be blacklisted are
>> actually blocked?
>> ​
>>
>> Filed CentOS bug report 7977 
>> this morning.  ipset was working great most of the year until ipset 6.11.-3
>> CentOS bug 7977​ 
>>
>
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS-announce Digest, Vol 118, Issue 6

2014-12-10 Thread centos-announce-request 
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CEBA-2014:1970  CentOS 6 dovecot BugFix Update (Johnny Hughes)
   2. CEBA-2014:1969  CentOS 7 qemu-kvm BugFix Update (Johnny Hughes)
   3. CESA-2014:1974 Important CentOS 6 rpm SecurityUpdate
  (Johnny Hughes)
   4. CESA-2014:1974 Important CentOS 5 rpm SecurityUpdate
  (Johnny Hughes)


--

Message: 1
Date: Tue, 9 Dec 2014 14:57:03 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CEBA-2014:1970  CentOS 6 dovecot BugFix
Update
Message-ID: <20141209145703.ga51...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Bugfix Advisory 2014:1970 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1970.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
60b713a7c88f9fbebd814a37c9dd08433069021f669650e24f6da134932d2b13  
dovecot-2.0.9-8.el6_6.1.i686.rpm
8df37000802b038252439fc3906e38034a049b026b0f5700fadfc84fc0723004  
dovecot-devel-2.0.9-8.el6_6.1.i686.rpm
5b36a701688f0274fc89a31b13a34e5a9758875dc28ce01515c9074cc807cf41  
dovecot-mysql-2.0.9-8.el6_6.1.i686.rpm
b719f54e59db6014fff1e7a2f78c0767a102d74c53305f67cf7b62e2a1251f5a  
dovecot-pgsql-2.0.9-8.el6_6.1.i686.rpm
62b969e2a9269e619921c151f2292a97cbd2b784bd4314fb13ceaa4d9e999309  
dovecot-pigeonhole-2.0.9-8.el6_6.1.i686.rpm

x86_64:
60b713a7c88f9fbebd814a37c9dd08433069021f669650e24f6da134932d2b13  
dovecot-2.0.9-8.el6_6.1.i686.rpm
fedc17d8cd7f55e74e9a701a0b5696e65ba53fc384d0e680c81fddc5a9d8486e  
dovecot-2.0.9-8.el6_6.1.x86_64.rpm
c96fb733663acaa57c2bee2f67651e1209ac7b85106d31c5358b2d70b888750e  
dovecot-devel-2.0.9-8.el6_6.1.x86_64.rpm
7aee52329db15389bd3e0304df0165ff4048ff93b31c60158382a695040b7cdd  
dovecot-mysql-2.0.9-8.el6_6.1.x86_64.rpm
7add0f3fb4d4bb7262dc52d50aafb237d3601e4bb30315644bd11c5699803793  
dovecot-pgsql-2.0.9-8.el6_6.1.x86_64.rpm
ed820ee36ee7cb7c99b90215c2378a111ac6ca81e1ee54c132b46368c9e9bfec  
dovecot-pigeonhole-2.0.9-8.el6_6.1.x86_64.rpm

Source:
91202afaf263076b3f3afb2a8f2591d65506b4066425f4160f1c99ca086c497d  
dovecot-2.0.9-8.el6_6.1.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

Message: 2
Date: Tue, 9 Dec 2014 15:22:28 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CEBA-2014:1969  CentOS 7 qemu-kvm BugFix
Update
Message-ID: <20141209152228.ga62...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Bugfix Advisory 2014:1969 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1969.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
7bb6a67af8966c6d7f8541742a80120588c3e3304ee1200c5834135551cd7f2f  
libcacard-1.5.3-60.el7_0.11.i686.rpm
27e0f6d8782ae092c0decd9f86a850e7e49b69897fbfb1693d184ca6c8daa7dd  
libcacard-1.5.3-60.el7_0.11.x86_64.rpm
2a14f9b94061686b5c5b8653ec25f31c500bcd1bd7f1a428e86ad3fa659bf884  
libcacard-devel-1.5.3-60.el7_0.11.i686.rpm
cb78e295a62161e6a63594b929951ee49c2f5fc88192aa303db45f3cf346dc5f  
libcacard-devel-1.5.3-60.el7_0.11.x86_64.rpm
43fe873b1e478e0a05c92a06a5887ffc79ae202bdfd9d143fcb9ae7bc39f1302  
libcacard-tools-1.5.3-60.el7_0.11.x86_64.rpm
d92ef7bb2f6a65fe4ad40e2e284b6b63f8b99d52fc8d6ac7d8007618482c8870  
qemu-guest-agent-1.5.3-60.el7_0.11.x86_64.rpm
5a40981a8021e16782763cde8097554327d3eddf08ea7e0f9b2f1ccec9ccc9e2  
qemu-img-1.5.3-60.el7_0.11.x86_64.rpm
326e5088e8d34d45d52d2738dbe9c4611efb30d9da092dbf1dbdd2e9dd16e80f  
qemu-kvm-1.5.3-60.el7_0.11.x86_64.rpm
369861ce4cff38942f9a1b50cc49a0feb208077b41894e1e00b2c9e4e9e102c5  
qemu-kvm-common-1.5.3-60.el7_0.11.x86_64.rpm
b0f3cc3ec207bf8b6556e1b11e438c27a64f3476679361d5f3e3218bd79a21cd  
qemu-kvm-tools-1.5.3-60.el7_0.11.x86_64.rpm

Source:
8ffc1503525ba5ce6b76d765baf15b49f15d0f7e5369184aaafa60c689e062b8  
qemu-kvm-1.5.3-60.el7_0.11.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

Message: 3
Date: Tue, 9 Dec 2014 20:01:37 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2014:1974 Important CentOS 6 rpm
SecurityUpdate
Message-ID: <20141209200137.ga6...@n04.lon1.karan.org>
Content-Type: tex

Re: [CentOS] get /full/path/filename.ext from filename.ext

2014-12-10 Thread ken 

On 12/09/2014 08:11 PM, Jonathan Billings wrote:

On Tue, Dec 09, 2014 at 03:57:03PM -0500, ken wrote:

You'd think this functionality would be included already in one or
another linux utility.  It's kinda like the complement to the
'basename' utility.  I've looked into the dark corners of ls, stat,
file, bash, type, find, and a few other linux standards, but nothing
seems to do this.


'readlink -f FILE'

The -f (or --canonicalize) follows symlinks and prints the canonical
path.



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

Re: [CentOS] NSS update issues.

2014-12-10 Thread Lamar Owen 

On 12/09/2014 05:22 PM, Chris Stone wrote:

On Tue, Dec 9, 2014 at 2:30 PM, Lamar Owen  wrote:


Ok, so how do I fix this (other than 'yum downgrade nss firefox
nss-sysinit nss-devel nss-tools' which does 'fix' the issue)?
Try installing the Firefox 'SSL Version Control' add-on. Had this 
issue with Fedora 20 and install this add-on and set it to TLS 1.0.


That worked; thanks much, Chris.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] NSS update issues.

2014-12-10 Thread Johnny Hughes 
On 12/09/2014 03:30 PM, Lamar Owen wrote:
> Ran into a bit of a sticky wicket today.  And for reasons that should be
> obvious it was a bit difficult to google for a solution, so I backed out
> the upgrade.  So I'm hoping someone here has seen and fixed this already.
> 
> System: CentOS 7, fully updated.  After the nss updates in the past day
> or so, visiting https://www.google.com with Firefox results in the
> following error screen:
> Secure Connection Failed
> 
> An error occurred during a connection to www.google.com. The server
> rejected the handshake because the client downgraded to a lower TLS
> version than the server supports. (Error code:
> ssl_error_inappropriate_fallback_alert)
> 
> The page you are trying to view cannot be shown because the
> authenticity of the received data could not be verified.
> Please contact the website owners to inform them of this problem.
> Alternatively, use the command found in the help menu to report this
> broken site.
> 
> Ok, so how do I fix this (other than 'yum downgrade nss firefox
> nss-sysinit nss-devel nss-tools' which does 'fix' the issue)?

Can someone verify this is also an issue on RHEL-7 ... looks like
something that needs to be fixed if only older TLS versions are supported.




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7 install software Raid on large drives error

2014-12-10 Thread Devin Reade 

For RAID-1 on CentOS 7, have a look at the following:


It deals with the situation, including mirroring of /boot.  Note
that in my case, I disabled UEFI in the BIOS, so didn't have
/boot/efi come up on autopartition.

That URL also implies a not-stellar assessment of getting help
on this list.  In that particular case, the assessment was IMO
accurate.  ie: If you're going to answer the question, then
answer the question and don't go off on a tangent.

Devin

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

Re: [CentOS] NSS update issues.

2014-12-10 Thread Devin Reade 
--On Wednesday, December 10, 2014 09:14:56 AM -0600 Johnny Hughes
 wrote:

> Can someone verify this is also an issue on RHEL-7 ... looks like
> something that needs to be fixed if only older TLS versions are supported.

I don't have RHEL7 (*cough*) installed on a desktop yet, but I disabled
SSL version control in RHEL6 and didn't see the issue come up.  Not quite
the data point you're looking for ...




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

Re: [CentOS] CentOS-6.6 - Selinux and Postfix-2.11.1

2014-12-10 Thread James B. Byrne 

On Tue, December 9, 2014 18:45, Alexander Dalloz wrote:
> Am 09.12.2014 um 23:04 schrieb James B. Byrne:
>> Applied policy update. Now I see these occasionally. But by the time I try
>> and
>> see what the matter is the file is gone:
>
> Why do you start a new thread instead of continuing the old one about
> the very same topic?
>

If you have a way to thread digest messages then I am open to suggestions.


-- 
***  E-Mail is NOT a SECURE channel  ***
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

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

[CentOS] No package group "X Window System" in CentOS 7.0?

2014-12-10 Thread Niki Kovacs 

Hi,

I'm currently experimenting with CentOS 7.0 in a few virtual guests, 
trying to install a reduced GNOME desktop as well as a minimal KDE 
desktop. I'm following this documentation:


http://www.dokuwiki.tachtler.net/doku.php?id=tachtler:centos_7_-_minimal_desktop_installation

I'm stuck at this point:

# yum groupinstall "X Window System"

Now I remember this from CentOS 5.x, when I began desktop installations 
with a minimal base system, then I added X11, configured it (using the 
minimal TWM), then added GNOME, then applications as needed.


Now there seems to be no more "X Window System" group. At least 'yum 
grouplist' knows nothing about it.


Any suggestions?

Cheers,

Niki
--
Microlinux - Solutions informatiques 100% Linux et logiciels libres
7, place de l'église - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] CentOS 7 grub.cfg missing on new install

2014-12-10 Thread Jeff Boyce 

Greetings -

The short story is that got my new install completed with the partitioning I 
wanted and using software raid, but after a reboot I ended up with a grub 
prompt, and do not appear to have a grub.cfg file.  So here is a little 
history of how I got here, because I know in order for anyone to help me 
they would subsequently ask for this information.  So this post is a little 
long, but consider it complete.


Brand new Dell system with two 3GB drives in this system with RAID1 LVM 
taking all the space outside the boot partitions.  I initially created the 
sda[1,2] and sdb[1,2] partitions via GParted leaving the remaining space 
unpartitioned.  A gpt partition table was put on both drives.  During 
installation Anaconda recognized everything properly which resulted in the 
following partition summary:


sda1 /boot/efi 500 MB EFI System Partition
sda2 /boot 500 MB xfs
vg_jab-hostroot / 8 GB LVM xfs RAID1
vg_jab-hostvar /var 4 GB LVM xfs RAID1
vg_jab-hostswap /swap 2 GB LVM swap RAID1

The installer also recognized and listed these unknown partitions that were 
untouched during installation.

sdb1 vfat 500 MB standard partition
sdb2 vfat 500 MB standard partition

Installation proceeded successfully, and after the initial reboot of the 
system I used mdadm commands to watch the raid complete building before 
doing anything else (I know, not necessary but I am doing other things and 
had the time to let it complete).  I rebooted the system and got a terminal 
prompt as expected (no GUI installed).  At this point I needed to copy my 
/boot/efi and /boot partitions from sda[1,2] to sdb[1,2] so that the system 
would boot from either drive, so I issued the following sgdisk commands:


root#  sgdisk -R /dev/sdb1 /dev/sda1
root#  sgdisk -R /dev/sdb2 /dev/sda2
root#  sgdisk -G /dev/sdb1
root#  sgdisk -G /dev/sdb2

Results of the first command above:
  Found invalid GPT and valid MBR; converting MBR to GPT format.
  Warning the kernel is still using the old partition table.  The new table 
will be used at the next reboot.  The operation has completed successfully.
  The same note (from the Warning on) was repeated for the other three 
commands.


I then installed GRUB2 on /dev/sdb1 using the following command:
root#  grub2-install /dev/sdb1
   Results:  Installing for x86_64-efi platform.  Installation finished. No 
error reported.


I rebooted the system now, only to be confronted with a GRUB prompt. 
Thinking that this is a good opportunity to for me to learn to rescue a 
system since I am going to need to understand how to recover from a disk or 
raid failure, I started researching and reading.  It takes a little bit of 
work to understand what information is valuable when a lot of it refers to 
GRUB (not GRUB2) and doesn't make reference to UEFI booting and partitions. 
I found this Ubuntu wiki as a pretty good source

https://help.ubuntu.com/community/Grub2/Troubleshooting#Search_.26_Set

Below is the current information of my system as seen by grub;

grub#  set(the important grub2 variables are:)
   prefix = (hd1, gpt2)/grub2
   root = hd1, gpt2

grub#  ls -lha
   Device proc:  filesystem type procfs
   Device hd0:  no known filesystem detected
   Device hd1:  no known filesystem detected
   Partition hd1, gpt3:  no known filesystem detected
   Partition hd1, gpt2:  filesystem xfs
   Partition hd1, gpt1:  filesystem fat
   Device hd2:  no known filesystem detected
   Partition hd2, gpt3:  no known filesystem detected
   Partition hd2, gpt2:  no known filesystem detected
   Partition hd2, gpt1:  no known filesystem detected

grub#  ls (hd1, gpt2) -l /
   /efi
   /grub
   /grub2
   vmlinuz -3.10.0-123.el7.x86_64
   initramfs-3.10.0-123.el7.x86_64.img
   ... plus some other files

Looking through the directories, I see that there is no grub.cfg file. 
Other than grub not recognizing the filesystem on hd2, the directories on 
hd2, gpt[1,2] seem to be identical to hd1, gpt[1,2] as I would assume based 
on the sgdisk commands I gave to copy them.  My initial thinking is that I 
need to re-run grub2-install on hd1 (sda), but I need a running system to do 
that.  So following the guidance I had I issued the following commands in 
grub to boot the system.


grub#  linux /vmlinuz -3.10.0-123.el7.x86_64 root=/dev/sda2 ro
grub#  initrd /initramfs-3.10.0-123.el7.x86_64.img
grub#  boot

Unfortunately the system hung on booting, with the following information in 
the "journalctl" file:

#  journalctl
Not switching root: /sysroot does not seem to be an OS tree. 
/etc/os-release is missing.
Initrd-switch-root.service: main process exited, code=exited, 
status=1/FAILURE

Failed to start Switch Root.
. . . . .
Triggering OnFailure= dependencies of initrd-switch-root.service.
Sta

Re: [CentOS] print something on console after boot

2014-12-10 Thread Dan Hyatt 

I might be in left field but...

in init.d  create a script that simply

echo_ip

script contents
#!/bin/bash
ip -4 addr |grep inet |tee /var/log/ip  # this will only print the ip 
lines and copy to /var/log/ip ( I prefer tee over echo, for a variety of 
reasons)




then create S99echo_ip in rc3.d
so that it runs last





then On 12/8/2014 5:35 PM, Florin Andrei wrote:

CentOS 7

How do I print something on the text-mode console right after the OS 
has finished booting?


I've a virtual instance and I need to know its IP address after it has 
finished booting up, to know where to ssh into it. I've tried adding 
"ip -4 addr > /dev/tty0" to rc.local, but that obviously doesn't work, 
because the login prompt overwrites everything I do.




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

Re: [CentOS] get /full/path/filename.ext from filename.ext

2014-12-10 Thread Dan Hyatt 

I don't know if this is of interest as an alternative.

I did find a cool functionality called locate  and updatedb
Updatedb creates the database of your files, locate does superfast searches.

It essentially does a superfast "find" on your root filesystem, giving 
you the fully qualified path of all hits.

You can create db's on your other filessytems.

The problem is that it can get stale, but you can update it before doing 
your searches. Plus it gives you a fully qualified path name with the 
results.


So if you need to do a set of searches on a filesystem (or whole system)

run updatedb on each target filesystem to create the db for that filesystem.
then use locate to search each filesystem "db"...
it takes seconds like ls instead of minutes like findthe more files 
in the FS, the quicker the searches compared to other tools.


the best part is you can run the db's when your systems are quiet, and 
the databases use minimal diskspace.



On 12/9/2014 2:57 PM, ken wrote:

This should be simple, but it's not, unless I'm forgetting something.

Writing a script, an arg is a filename.  So

fname=$1

But I want that expanded to include the full path and filename, not 
just what is given as the arg on the command line.


E.g., if the user's cwd is /home/joe/a/b/c/ and he specifies

../x/file-a.ext

then the function/utility should transform that into the absolute path 
with filename:


/home/joe/a/b/x/file-a.ext

In the simplest scenario, the answer would be $PWD/file-a.ext, but 
that would by no means cover a portion of the possible scenarios.


You'd think this functionality would be included already in one or 
another linux utility.  It's kinda like the complement to the 
'basename' utility.  I've looked into the dark corners of ls, stat, 
file, bash, type, find, and a few other linux standards, but nothing 
seems to do this.


Any gurus out there know the utility which does this?

___
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] get /full/path/filename.ext from filename.ext

2014-12-10 Thread Keith Keller 
On 2014-12-10, Dan Hyatt  wrote:
> I don't know if this is of interest as an alternative.

It may or may not be, but it doesn't help the OP, who already knows
where the file is, and just wants the full absolute path.  locate will
not help him there, especially if there are multiple files with the same
filename.ext on that filesystem.

> I did find a cool functionality called locate  and updatedb

locate has been around for many many years, certainly since at least
CentOS 4, likely much earlier.

> The problem is that it can get stale, but you can update it before doing 
> your searches.

There is (or at least, there should be) a script in /etc/cron.daily 
which updates it nightly.

> So if you need to do a set of searches on a filesystem (or whole system)
> run updatedb on each target filesystem to create the db for that filesystem.

You can configure locate (in /etc/updatedb.conf) with which directories
to index or not index.  Then you do not need to maintain your own
indexes, you can simply use the single system index.

--keith

-- 
kkel...@wombat.san-francisco.ca.us


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

Re: [CentOS] print something on console after boot

2014-12-10 Thread Gordon Messmer 

On 12/10/2014 12:47 PM, Dan Hyatt wrote:
I've a virtual instance and I need to know its IP address after it has 
finished booting up, to know where to ssh into it. I've tried adding 
"ip -4 addr > /dev/tty0" to rc.local, but that obviously doesn't work, 
because the login prompt overwrites everything I do.


The easy answer would be: don't fight the login prompt.  "agetty" writes 
the contents of /etc/issue to the console before the login prompt.  If 
/etc/issue contains "\4" then agetty will print the IPv4 address to the 
console.


See the man page for agetty, and update /etc/issue.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] httpd listening only on IPv6 interface on CentOS 7

2014-12-10 Thread Warren Young 
I’ve held off reporting this since I thought it might just be some kind of 
fluke, but I’ve seen it now on three different boxes.

The symptom is that the stock configuration of Apache only listens for IPv6 
connections:

  $ netstat -na | grep :80.*LISTEN
  tcp6   0  0 :::80   :::*LISTEN

You should see a second line there for IPv4, but you don't:

  tcp0  0 0.0.0.0:80  0.0.0.0:*   LISTEN

The stock httpd.conf file just says “Listen 80” which is documented as 
listening on both IPv4 and IPv6. [1]  You’re supposed to need to go out of your 
way to get it to listen on just one or the other, but somehow CentOS 7’s Apache 
manages it.

Since I only need IPv4, I’ve managed to hack it into working by changing that 
line in /etc/httpd/conf/httpd.conf to:

  Listen 0.0.0.0:80

Why do I need to do this?



[1] https://httpd.apache.org/docs/2.4/mod/mpm_common.html#listen
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] CentOS 7 grub.cfg missing on new install

2014-12-10 Thread Ned Slider 
On 10/12/14 18:13, Jeff Boyce wrote:
> Greetings -
> 
> The short story is that got my new install completed with the
> partitioning I wanted and using software raid, but after a reboot I
> ended up with a grub prompt, and do not appear to have a grub.cfg file. 
> So here is a little history of how I got here, because I know in order
> for anyone to help me they would subsequently ask for this information. 
> So this post is a little long, but consider it complete.
> 
> Brand new Dell system with two 3GB drives in this system with RAID1 LVM
> taking all the space outside the boot partitions.  I initially created
> the sda[1,2] and sdb[1,2] partitions via GParted leaving the remaining
> space unpartitioned.  A gpt partition table was put on both drives. 
> During installation Anaconda recognized everything properly which
> resulted in the following partition summary:
> 
> sda1 /boot/efi 500 MB EFI System Partition
> sda2 /boot 500 MB xfs
> vg_jab-hostroot / 8 GB LVM xfs RAID1
> vg_jab-hostvar /var 4 GB LVM xfs RAID1
> vg_jab-hostswap /swap 2 GB LVM swap RAID1
> 
> The installer also recognized and listed these unknown partitions that
> were untouched during installation.
> sdb1 vfat 500 MB standard partition
> sdb2 vfat 500 MB standard partition
> 
> Installation proceeded successfully, and after the initial reboot of the
> system I used mdadm commands to watch the raid complete building before
> doing anything else (I know, not necessary but I am doing other things
> and had the time to let it complete).  I rebooted the system and got a
> terminal prompt as expected (no GUI installed).  At this point I needed
> to copy my /boot/efi and /boot partitions from sda[1,2] to sdb[1,2] so
> that the system would boot from either drive, so I issued the following
> sgdisk commands:
> 
> root#  sgdisk -R /dev/sdb1 /dev/sda1
> root#  sgdisk -R /dev/sdb2 /dev/sda2
> root#  sgdisk -G /dev/sdb1
> root#  sgdisk -G /dev/sdb2
> 
> Results of the first command above:
>   Found invalid GPT and valid MBR; converting MBR to GPT format.
>   Warning the kernel is still using the old partition table.  The new
> table will be used at the next reboot.  The operation has completed
> successfully.
>   The same note (from the Warning on) was repeated for the other three
> commands.
> 
> I then installed GRUB2 on /dev/sdb1 using the following command:
> root#  grub2-install /dev/sdb1
>Results:  Installing for x86_64-efi platform.  Installation finished.
> No error reported.
> 

The upstream docs (see below) seem to suggest 'grub2-install /dev/sdb'
rather than /dev/sdb1 (i.e, installing to the device rather than a
partition on the device). I don't know if this is the cause of your issue.

> I rebooted the system now, only to be confronted with a GRUB prompt.
> Thinking that this is a good opportunity to for me to learn to rescue a
> system since I am going to need to understand how to recover from a disk
> or raid failure, I started researching and reading.  It takes a little
> bit of work to understand what information is valuable when a lot of it
> refers to GRUB (not GRUB2) and doesn't make reference to UEFI booting
> and partitions. I found this Ubuntu wiki as a pretty good source
> https://help.ubuntu.com/community/Grub2/Troubleshooting#Search_.26_Set
> 

I found the upstream documentation for grub2 to be useful:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Working_with_the_GRUB_2_Boot_Loader.html

Included is a procedure for completely reinstalling grub2 which might
help you recover.

> Below is the current information of my system as seen by grub;
> 
> grub#  set(the important grub2 variables are:)
>prefix = (hd1, gpt2)/grub2
>root = hd1, gpt2
> 
> grub#  ls -lha
>Device proc:  filesystem type procfs
>Device hd0:  no known filesystem detected
>Device hd1:  no known filesystem detected
>Partition hd1, gpt3:  no known filesystem detected
>Partition hd1, gpt2:  filesystem xfs
>Partition hd1, gpt1:  filesystem fat
>Device hd2:  no known filesystem detected
>Partition hd2, gpt3:  no known filesystem detected
>Partition hd2, gpt2:  no known filesystem detected
>Partition hd2, gpt1:  no known filesystem detected
> 
> grub#  ls (hd1, gpt2) -l /
>/efi
>/grub
>/grub2
>vmlinuz -3.10.0-123.el7.x86_64
>initramfs-3.10.0-123.el7.x86_64.img
>... plus some other files
> 
> Looking through the directories, I see that there is no grub.cfg file.
> Other than grub not recognizing the filesystem on hd2, the directories
> on hd2, gpt[1,2] seem to be identical to hd1, gpt[1,2] as I would assume
> based on the sgdisk commands I gave to copy them.  My initial thinking
> is that

[CentOS] Dropbox on CentOS 6?

2014-12-10 Thread Niki Kovacs 

Hi,

I just spent a couple of unnerving hours trying to make Dropbox work on 
CentOS 6.6.


Is there a way that

1. Actually works?

2. Doesn't include jumping through burning loops?

Cheers from the sunny south of France,

Niki
--
Microlinux - Solutions informatiques 100% Linux et logiciels libres
7, place de l'église - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos