Tag Info

Hot answers tagged

3

Your firewall rules reject all incoming traffic. You tried to deal with this by manually appending rules to allow HTTP, HTTPS and MySQL connections, but this does not work since they are already rejected by a previous rule. Further, your system is running firewalld. To resolve the problem, you should use firewalld to manage your firewall rules. For ...


3

My question is, does CentOS 7 have some sort of feature that makes dropping packets impossible? No, but it has two features that make dropping packets far less likely: a kernel version that includes TPACKET_V3 for PF_PACKET sockets; a libpcap version that uses TPACKET_V3 for PF_PACKET sockets. Libpcap uses PF_PACKET sockets to capture on Linux 2.2 ...


2

Add the logic to your firewall such as: iptables -I INPUT -s 10.0.0.0/29 -p tcp --dport 22 -j ACCEPT iptables -I INPUT -p tcp --dport 22 -j DROP


2

First: It looks like you have an XFS filesystem, so of course resize2fs won't work (that's only for ext[234] filesystems). xfs_growfs, which you have already used, is the tool for growing XFS filesystems. Second, and more importantly: Your root filesystem is on a logical volume. There is no "root partition". There is a LVM "physical volume" (PV) on ...


2

It is fairly common that mail servers require a valid e-mail address and reject invalid ones. noreply@example.com (Ryan) is not a valid e-mail address. The wikipedia entry has some useful pointers, as well as references to the relevant RFC's. In practice you use either a bare email address: noreply@example.com or whatever display name followed by a ...


2

The fact is tar is successful, but prints out warning that those socket files are ignored GNU tar actually provides an option to suppress warnings. You could ignore the "socket ignored" errors using the below command which avoids running a find command that could take a long time to complete. tar --warning='no-file-ignored' -cpzf backup_name.tar.gz ...


2

To elaborate @sebix answer above, you need to modify sendername variable in jail.conf. For example sendername = Fail2ban.myserver Or you can replace 'myserver' with hostname -f so you don't need to hardcode the server name in configuration file in each server sendername = Fail2ban.`hostname -f`


2

It seems like this could be a routing issue. Since the VMs inside KVM can route independently of the host, the issue is not going to be your physical network connectivity, but rather your logical network connectivity. Check your default gateway and static routes, make sure those are configured properly. If your host cannot find a route back to the devices ...


2

take a look at logrotate and /etc/logrotate.conf. Typically for log files you want to use the built in command rather then just deleting.


2

You can just use this commands: rm -f messages-* rm -f access_log-* It will delete all old logs which starts with "messages-" and "access_log-"


2

This very much looks like a DNS configuration problem inside the VM. Start from looking at /etc/resolv.conf contents. My guess is that adding/removing interfaces may change routing table and this way influence name resolving. What happens when you change nameservers order? A result from host -v google.com. could help you find the correctly working nameserver ...


1

The dtrace you find on Oracle Linux is not the dtrace which comes with Linux systemtap and that you will find on every other Linux distribution. Rather, it is a port of Solaris dtrace provided by Oracle and only available on Oracle Linux. The two commands are completely different and have different purposes. The standard Linux kernel tracing facility is ...


1

The file format is specified in RFC1034 and parts of RFC1035. It is very old (1987), and not specifically defined for BIND or in light of current features. There is no great wisdom to be had here; it's like that by convention. The format is also designed to be used for things like caches, I believe, though in practice this usage must be terribly rare. In ...


1

The logs with numbers have been rotated, best thing to do then is to compress each rotated log and have a script or cron to move those off the server and onto some persistent file store, for example, s3. If you don't really care about preserving logs for whatever reason, you can always rm someRotatedLog.log.000 and then echo "" > someCurrentLog.log so ...


1

I've just been struggling with this myself. Isn't ePages fun? There a number of ways in which the ePages Apache configuration differs from a more "normal" site. 1. It rewrites most of the config files every time the ePages service restarts. Anything with a "zzz" prefix (which is most of the files in conf.d) will be rewritten, so don't bother editing those ...


1

Once you define a first vhost on port *:80, all your port 80 traffic is handled by that vhost as opposed to the base webserver configuration. Usually the best way to proceed is to create two *:80 vhosts. The first one defined is the default will cover everything your base config used to handle -- the second specifies ServerName/ServerAlias to capture the ...


1

This bug is documented upstream in https://access.redhat.com/solutions/508303 and so far the solution indeed is to disable the acpi_pad driver. On my systems (IBM Flex x240) this happens after disabling Hyperthreading.


1

Start with connectivity from the CentOS box. Can you ping any other hosts on the network? If not, then you need to figure out what's going on there. Is the IP address in the same subnet as the other hosts on the network? You don't give any information about what IP and subnet mask the various hosts are set up with, or what your network looks like, so any ...


1

nmap will give following output though both hosts are not in same subnet ! ashish@ashishk:~/chef-repo/.chef$ nmap -p7 -Pn 172.31.4.235 Starting Nmap 6.40 ( http://nmap.org ) at 2015-08-25 15:25 IST Nmap scan report for 172.31.4.235 Host is up. PORT STATE SERVICE 7/tcp filtered echo Nmap done: 1 IP address (1 host up) scanned in 2.24 seconds But you ...


1

As your error message shows, the mysql command is trying to connect via a UNIX socket, not a TCP socket, and consequently ignores the port number. This is what mysql does if you give localhost as the host argument. Try using -h 127.0.0.1 instead.


1

Just create two sections Match in the config that define required behaviour: Match Address 11.22.33.44/29 AllowUsers * Match Address * AllowUsers


1

when you do ps aux | grep cron you are running two commands - ps aux and grep cron. ps aux lists all processes currently running, and grep cron matches any lines which contain "cron" in them. Obviously the crond process matches the word cron, but so does the grep cron process you just ran. It's matching itself recursively.


1

Based on the error message, it sounds like ngrep is selecting a non-existent device to sniff. If you add -d eth0 (or whichever interface you expect to see the traffic passing over) you may have better luck. Also, one rather annoying "gotcha" I seem to recall from using ngrep in the deep, dark, distant past, you need to specify a pattern when you're also ...



Only top voted, non community-wiki answers of a minimum length are eligible