Tag Info

Hot answers tagged

5

firewalld ships with a default set of predefined ICMP types you can use out of the box: # firewall-cmd --get-icmptypes destination-unreachable echo-reply echo-request parameter-problem redirect router-advertisement router-solicitation source-quench time-exceeded timestamp-reply timestamp-request The parser ...


3

As it told you specifically: # WARNING: If you enable this repository, you must also enable "remi" You have also installed the remi repositories for EL6, but you are actually running EL7. You also need to correct this by using the EL7 repos instead. The easiest way to do this is to install the appropriate remi-release RPM for EL7.


3

Start by investigating the relations between parent/child processes using a command such as ps -AF --forest. The Parent Process ID (PPID) will either be the process that spawned the process in question, or 1 if it forked or became orphaned. The --forest switch to PS displays a graphical representation of this relationship. Deamons are usually started with ...


3

Your server block doesn't have a root directive defined. Instead it seems to be in one of your location blocks. This is one of the most common nginx mistakes. Move it under the server block instead.


2

In your ifcfg-eth0 file: DOMAIN=example.com or DOMAIN="example.com sub.example.com" The domain and search directives in resolv.conf are mutually exclusive. They've been going back and forth upstream on how exactly to handle it. If DOMAIN doesn't work, try SEARCH.


1

The shodanshok's comment is right: If you can't telnet the SMTP server, the connection is blocked at the gateway or server level. So I opened a ticket for Digital Ocean's support and got the following response: To curb a recent increase in abuse and SPAM, we have an initial SMTP block on new accounts created in certain contexts. To remove ...


1

SELinux is probably not allowing nginx to access the /home directory. Try changing the root to /var/www as a test. Also when you are starting up nginx run journalctl -x in a different session to see the error messages and post them here.


1

Probably better explain us what you really have in mind. The command would be (from the top directory) : find . -type f -name '*.php' -exec sed 1d -i '{}' \;


1

On a solaris SunOS xxxxxxxxxx5.10 Generic_150400-18 sun4v sparc SUNW,T5240 I built the modd_ssl with the following features installed in the apache module dir edited httpd.conf to include LoadModule ssl_module modules/mod_ssl.so bash# apxs -L/path/to/openssl/dir -I/path/to/openssl/dir/include -Wc,-fPIC -i -a -c mod_ssl.c


1

Upgrade your C compiler. See here GCC version is too old


1

Please try with stopping or disabling the exim service because postfix can conflict with exim when both software were running. #service postfix stop #rm -rf /var/lock/subsys/postfix #rm -rf /var/spool/postfix/pid/master.pid #service exim stop #chkconfig exim off #service postfix start Your postfix will be running without dead.


1

I just fixed the same problem. My vmbuilder created an image with a root partition followed by a swap partition. cloud-utils-growpart can't grow the root partition if there's one immediately after it. I deleted the swap partition and the root partition resized correctly on reboot


1

systemd completely ignores /etc/security/limits*. If you are using an RPM that auto-squashes its systemd service file on update, you'll want to file a PR to ask them to mark those files as 'noreplace' You need to update the .service file (/usr/lib/systemd/system/(yourthing).service [Unit] Description=Some Daemon After=syslog.target network.target ...



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