Moved from Hostinger Shared to Hostinger Cyberpanel VPS.
OS: Centos 7
CyberPanel: v2.3.2
Problem:
Server > Security > ModSecurity Conf > Install Now > "Installation failed. None"
Text*
Loaded plugins: copr, fastestmirror, priorities
Loading mirror speeds from cached hostfile
* base: mirror.centos.iad1.serverforge.org
* epel: mirror.coastal.edu
* extras: mirror.dal.nexril.net
* updates: mirror.centos.iad1.serverforge.org
10 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package ols-modsecurity.x86_64 0:1.7.16-2.el7 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
ols-modsecurity x86_64 1.7.16-2.el7 litespeed-update 16 M
Transaction Summary
================================================================================
Install 1 Package
Total size: 16 M
Installed size: 71 M
Downloading packages:
Running transaction check
Running transaction test
Can not be installed.[404]
End Text
What I've done:
Reinstalled the OS: Centos 7
Contacted the following support:
Hostinger
Cyberpanel both paid support and the community.
Results:
Waiting for replies, no solution.
Problem Solved! Hostinger support gave me the right guidance to solve this problem.
Note: The following is what I did. I'm using a Mac running macOS Catalina. Window folks will need Pudy. Also, this worked for my specific situation described in my first post.
On Mac, make sure the Terminal can run "zsh shell". I rarely use the Terminal, when I opened it there was some command that I needed to run to get the terminal to run 'zsh'. Like I said, Newbie here.
(Article reference: https://eshop.macsales.com/blog/56921-moving-from-bash-to-zsh-terminal-changes-in-macos-catalina/)
Terminal now set to run Zsh shell, I went to my Cyberpanal > Overview > VPS access > Terminal > copied the text paste into Terminal.
Pasted my root password.
I went to the following article: https://manage.accuwebhosting.com/knowledgebase/3766/How-to-install-mod-security-on-Centos-7-x-with-apache-.html
Under heading: "Please refer to the following steps to install mod security on ContOS 7.X:
Only did steps 1 and 2. Step 3 is optional if you're curious.
Finally, I went back to CyberPanel > Security > ModSecurity Conf > Install Now
Result: Success!
Related
I tried to install the DB2 V11.1 FP5 on a SLES-12-SP4 machine. So far I
downloaded the universal package
extracted the universal package
called the command "./installFixPack -b /opt/ibm/db2/V11.1/ -p /opt/ibm/db2/fp5/" as root user
But the installFixPack stopps working sometimes at step 44 or 47 or also step 50 of 73 without any clear error message. In the log file I find a message like
"ERROR: The install path "/opt/ibm/db2/fp5" is invalid. Specify a
valid install path.
ERROR: DBI20105E An error occurred while installing the following
file set: "DB2_PRODUCT_MESSAGES_FR_11.1.4.5_linuxamd64_x86_64".
Because these files were not successfully installed, functionality
that depends on these files might not work as expected.
Rolling back what has been installed"
Any hint what I'm doing wrong?
Thanks so much for reading so far
best regards
Thomas Graf
./installFixPack -b is to patch an aleady installed DB2 HOME cf: pass from FP4 To FP5.
if you want to install the FP5 into a new path use db2setup (or ./db2setup -r for silent install)
you should add -l /var/tmp/installlog.log -t /var/tmp/installtrace.log to the installFixPack to see exactly what is the error.
Even if you started the install with root, the app can use another user to install some files/libraries.
Do you have the same message after manually creating this folder ?
I have a Linux server that is running Debian squeeze, I can not run apt-get update on it. I get errors like these:
W: Failed to fetch http://ftp.us.debian.org/debian/dists/squeeze/main/binary-i386/Packages.gz
Unable to connect to 10.197.3.5:3142:
I can successfully ping ftp.us.debian.org ,but the ip address that it shows is different than the ip address shown with the unable to connect message.
I assumed this was an issue with DNS translation, so I changed my DNS server to google's 8.8.8.8 server
Running dig google.com
shows that the DNS server is in fact the google server I specified.
I'm stumped. It may be of note that I am forwarding port 22 and port 80 to my router so my teammates can ssh and view the webpage associated with this server. I don't think this is the issue since this occurs even when I stop the forwarding.
Turns out the original holder of this server set up a proxy in /etc/apt/apt.conf that wasn't working, (I don't know why this was)
I remove this line form that file
Acquire::http::Proxy "PROXYIP/apt-cacher/";
I have fixed similar issue applying one comment about your issue:
My environment is:
Linux debianlpi 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64 GNU/Linux
The issue that I got, was:
root#debianlpi:~# apt-get install vim
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
vim-runtime
Suggested packages:
ctags vim-doc vim-scripts
The following NEW packages will be installed:
vim vim-runtime
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 5,999 kB of archives.
After this operation, 28.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
WARNING: The following packages cannot be authenticated!
vim-runtime vim
Install these packages without verification? [y/N] y
0% [Connecting to idcproxy.compabc.com (432.1.2.20)]
It was fixed removing line in /etc/apt/apt.conf:
root#debianlpi:~# cat /etc/apt/apt.conf
#Acquire::http::Proxy "http://idcproxy.compabc.com:80";
After repeated attempts and trying to google this issue I'm stuck and am looking for help from my fellow stackers.
Following the wiki from tcadmin I have to run the following commands
wget http://www.tcadmin.com/installer/mono-2.11.4-i386.rpm
yum -y install mono-2.11.4-i386.rpm --nogpgcheck
/opt/mono-2.11.4/bin/mozroots --import --sync --quiet
/opt/mono-2.11.4/bin/mono --aot -O=all /opt/mono-2.11.4/lib/mono/2.0/mscorlib.dll
for i in /opt/mono-2.11.4/lib/mono/gac/*/*/*.dll; do /opt/mono-2.11.4/bin/mono --aot -O=all $i; done
when I get to the yum part it fails and outputs this error.
file / from install of mono-2.11.4-bi.x86_64 conflicts with file from package filesystem-3.2-18.el7.x86_64
Most sites and places suggest using an override or force command but this sounds stupid and will probably cause issues down the road for myself and the system.
I have flagged a ticket with the company that supplies the wiki about this issue but I'm yet to have a reply.
Another suggestion was to extract the rpm and move the files one by one but this is quite time consuming..
The ticket was responed to with the following;
It is safe to force install because all files are placed in /opt/mono-2.11.4 but there is a bug with mono on centos 7 that prevents tcadmin from working correctly.
For anyone else who happens upon this thread, I'm pleased to report that while I didn't encounter this error installing mono (that was a whole other process) I did encounter it while trying to install TCAdmin itself, but I was able to complete the installation of TCAdmin on CentOS 7 after using rpmrebuild to modify the spec.
Simply install rpmrbebuild, run rpmrebuild -pe {packagename}.rpm, scroll down to the %files section and remove the lines for any offending directories (in my case, the '/' and '/home' directories), save and quit, press y, and note the result location. In my case, it was /root/rpmbuild/RPMS/noarch/{packagename}.rpm.
Traverse to that directory and run yum -y install ./{packagename.rpm and it will install without a hitch.
The same should also apply to any other packages that return the conflicts with filesystem error. Just adjust the package names in the above examples accordingly.
*Thanks to the venerable Ahmad Samir for pointing me in the right direction with his post in this thread.
I had the same issue trying to install Fluentd agent on CentOS 7:
(venv)[user#machine01 tmp]$ sudo rpm -ivh td-agent-2.1.1-0.x86_64.rpm
warning: td-agent-2.1.1-0.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID a12e206f: NOKEY
Preparing... ################################# [100%]
file /opt from install of td-agent-2.1.1-0.x86_64 conflicts with file from package filesystem-3.2-18.el7.x86_64
I wouldn't say that downgrading your whole OS is the solution. Maybe an elegant workaround would be to rebuild the .rpm file in order to avoid those file systems which are making conflicts. You can do this by modifying the spec file with rpmrebuild command.
However, if you trust the software you are about to install or you want to try if works no matter what, then an easier (and faster) workaround is to force the rpm installation. That's what I did ...
(venv)[user#machine01 tmp]$ sudo rpm -ivh --force td-agent-2.1.1-0.x86_64.rpm
warning: td-agent-2.1.1-0.x86_64.rpm: Header V4 DSA/SHA1 Signature, key ID a12e206f: NOKEY
Preparing... ################################# [100%]
Updating / installing...
1:td-agent-2.1.1-0 ################################# [100%]
adding 'td-agent' group...
adding 'td-agent' user...
Installing default conffile...
prelink detected. Installing /etc/prelink.conf.d/td-agent-ruby.conf ...
Configure td-agent to start, when booting up the OS...
...and it worked for me
(venv)[user#machine01 tmp]$ sudo systemctl start td-agent.service
(venv)[user#machine01 tmp]$ sudo systemctl status td-agent.service
td-agent.service - LSB: td-agent's init script
Loaded: loaded (/etc/rc.d/init.d/td-agent)
Active: active (running) since vie 2014-12-12 09:34:09 CET; 4s ago
Process: 17178 ExecStart=/etc/rc.d/init.d/td-agent start (code=exited, status=0/SUCCESS)
...
Hope it helps
This is an inherent issue with centos 7.
Going back to centos 6 fixed it.
I am trying to get Mono working on nginx with fastCGI.
I have done a fresh install of CentOS 6, and performed all the updates. I then installed nginx, and opened up the firewalls I needed. I can now see the simple HTML page from nginx without a problem.
I then followed this tutorial for installing Mono via Git :
https://stackoverflow.com/a/13424880/221456
libgdiplus installed fine
mono installed fine
xsp, when I run autogen (with the prefix), gives me this error :
checking for MONO_MODULE... configure: error: Package requirements
(mono >= 2.10.0) were not met:
No package 'mono' found
I did a bit of searching, and the only thing I could find was to run this command :
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
Which I have tried, however I still get the exact same error message.
What am I missing?
The problem is with the variable
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig
the correct is
export PKG_CONFIG_PATH=/usr/lib/pkgconfig
because you compile with the with the prefix. /usr
I've got an error regarding to R CMD check in R-forge repository. when it checks with windows and mac platform it doesn't give an error except one note which is regarding to maintainer. how ever, it doesn't check correctly regarding to Linux platform and gives me the following error. due to this error I couldn't submit my package to cran. Please help me how to solve the problem.
BcDiag log file (check_x86_64_linux)
Sun Dec 30 16:15:16 2012: Checking package BcDiag (SVN revision 7) ...
* using log directory ‘/mnt/building/build_2012-12-30-16-05/RF_PKG_CHECK/PKGS/BcDiag.Rcheck’
* using R version 2.15.2 Patched (2012-12-14 r61333)
* using platform: x86_64-unknown-linux-gnu (64-bit)
* using session charset: UTF-8
* checking for file ‘BcDiag/DESCRIPTION’ ... OK
* this is package ‘BcDiag’ version ‘1.0’
* checking CRAN incoming feasibility ... NOTE
Maintainer: ‘Aregay Mengsteab ’
New submission
* checking package namespace information ... OK
* checking package dependencies ... ERROR
Packages required but not available: ‘isa2’ ‘fabia’
Packages suggested but not available for checking: ‘isa2’ ‘fabia’
Regards,
Mikeal.
This may be an issue with R-Forge's build server; I have the same issue with another package where a dependency is no longer available but which is available on CRAN and builds/checks OK there. My package checks OK on Linux but not on R-Forge. When I submitted it to CRAN it passed their checks too.
With changes in the last version of R to be released, package libraries have needed to be rebuilt. This may be related to the problems on R-Forge?
Anyway, Suggest you file a support ticket or email the R-Forge team to enquire. If that package builds/checks OK on your own computer, then it is probably safe to submit to CRAN. If you want to be doubly sure, perhaps submit the package to Uwe Ligge's WinBuilder service to get an independent compile/build/check. If that works OK, then you can be reasonably sure your package is OK to submit to CRAN.