Centos – How to solve – Failed to execute operation: Too many levels of symbolic links on CentOs 7

centosnginxsymlink

I am trying to install erpNext on a CentOS 7.4 VPS and I'm following the installation script here. But I get this error during installation:

Processing dependencies for pip
Finished processing dependencies for pip
Configuring CentOS services
Created symlink from /etc/systemd/system/multi-user.target.wants/nginx.service to /usr/lib/systemd/system/nginx.service.
Failed to execute operation: Too many levels of symbolic links

How I do I fix this error? My guess is there's a problem with the setup file but I'm new to this so I don't know where to look.

Best Answer

This is because your service is using symbolic link so remove symbolic link and try.

It should work

Related Solutions

Tomcat 8 – Troubleshooting Initial Install Startup Issues

I had the same problem, fixed it by:

giving tomcat user ownership of the whole tomcat directory:
```
cd /opt && sudo chown -R tomcat tomcat/
```

and commenting out below line in /etc/systemd/system/tomcat.service:

Environment='CATALINA_OPTS=-Xms512M -Xmx1024M -server -XX:+UseParallelGC'

linux centos kernel – Kdump.service FAILED on CentOS 7

Install the required packages

yum --enablerepo=debug install kexec-tools crash kernel-debug kernel-debuginfo-`uname -r`

Modify grub

A kernel argument must be added to /etc/grub.conf to enable kdump. It’s called crashkernel and it can be either auto or set as a predefined value e.g. 128M, 256M, 512M etc.

The line will look similar to the following:

GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/swap crashkernel=auto rd.lvm.lv=rhel/root rhgb quiet"

Change the value of the crashkernel=auto to crashkernel=128 or crashkernel=256 ...

Regenerate grub configuration:

grub2-mkconfig -o /boot/grub2/grub.cfg

On a system with UEFI firmware, execute the following instead:

grub2-mkconfig -o /boot/efi/EFI/Centos/grub.cfg

Open the /etc/zipl.conf configuration file

locate the parameters= section, and edit the crashkernel= parameter (or add it if not present). For example, to reserve 128 MB of memory, use the following:crashkernel=128M save and exit

Regenerate the zipl configuration:zipl

⁠Enabling the Service

To start the kdump daemon at boot time, type the following command as root:

chkconfig kdump on

This will enable the service for runlevels 2, 3, 4, and 5. Similarly, typing chkconfig kdump off will disable it for all runlevels.

To start the service in the current session, use the following command as root:

service kdump start

Best Answer

Related Solutions

Tomcat 8 – Troubleshooting Initial Install Startup Issues

linux centos kernel – Kdump.service FAILED on CentOS 7

Related Question